Patch for some temp fixes and enhancements about meteor-collectionfs HOT 2 CLOSED

Thanks @petrocket, its nice to get such constructive feedback :) I'm glad it comes to use,
I'll take a pull request to the devel branch, your wellcome to add doc to the README.MD - Hope the Meteor guys will soon implement the new packages + documentations specs

(I see you've added delete and update that's great! - maybe a comment / todo: The remove should call a server method or have add an observer for deleting the chunks and cache files related)

The publish method takes an extra option when autopublishing: {is_auto: true} It's not documented but it stops the console warnings when using the autopublish package.

Meteor.publish(self._name+'.files', function () { //TODO: nullable? autopublish?
    return self.files.find({});
}, {is_auto: true});

nr. 2 Is a wierd async one, but I agree it's nice to be able to see how many chunks actually landed safely in the db, could be nice with a handlebars helper {{progress}} for the actual upload/download status.

Btw.: Do you have any stats/issues on upload speeds?
It's using the ddp protocol, I'm thinking about testing changing to BSON eg.: data: { binary: data } - If speed still an issue then perhaps setting up a seperate server instance for dedicated
upload/download.

from meteor-collectionfs.

Pull request submitted! Not sure if I did that right - first time and all.

I've been using CollectionFS on a site where I upload lots of images (~100K - 500K) and make thumbnails. Speed doesn't seem to be an issue for me. The biggest problem so far is that there doesn't seem to be any throttling on the number of simultaneous uploads so occasionally the server runs out of memory when I upload 20+ images and the server is trying to create thumbnails (I don't write the original files to disk, just the resized images).

BSON might be a good option for large files, which will be necessary to support for many other kinds of apps but for small uploads ddp is fine I think.

from meteor-collectionfs.