Well sort of. CollectionFS as I understand it ran all file management through the Meteor (node) server. This has actually caused me trouble in the past as it would use a temp file in whatever backing store you specified, which caused trouble during startup when scaling my apps. (That’s just an implementation detail that could have been fixed in reality)
Slingshot uses auth tokens to allow the client to deliver files directly to the backing store in a secure way, without routing through the server.
What I’m looking for is something like a Collection interface (ideally it wouldn’t need to use any Mongo resources, though I suspect it would be useful to store some cached meta data there) to manage the files once they are whatever file storage service. Currently you just get a URL back after uploading a file through Slingshot. Slingshot itself doesn’t seem to offer any real management API (deleting files, listing files, etc.) unless I’ve missed it.
Ok Grow’s REST2DDP package may actually be useful here. When I get some time I’ll investigate using that.