different upload storage methods

Hi Karls,

>Is this something you working on?

Yes, we're adding support for storing uploads in Amazon S3 as a first step.

>Have you any plan to change the upload to HTML5 from Flash to make multiple upload system compatible for every device?

Yea, also on our list.  We're using an older version of http://www.uploadify.com/ and we want to upgrade to a newer version of that or http://www.plupload.com/ that supports HTML5 uploads, and chunked uploads (for upload very large files without timing out).

No timelines yet, though.

Hi Dave,

Yes, i'm working on a platform for a digital printing studio, where photographers can upload their works and order different printed materials with the uploaded photos (like albums, printed canvas, etc). This would be ideal with the new upload system with external storage (because storage space and upload speed). In my case photographer's uploads for every event is usually about 500-750 megabyte, that for a my client is a huge server cost normally compared with a 3rd party storage solution.

HTML5 multiple (easy to use and/or drag & drop) upload solution is also very critical for apple and mobile devices that are widely used by photographers.

I'll try to create a hybrid solution where the uploads are go to a separated folder by user/event but after a smaller/resized image is storing somehow into the CMSB. Is there any part of the current upload system, that i can separate for the thumbnail creation and image storing in the MySQL database?

Originally i wanted to use https://blueimp.github.io/jQuery-File-Upload/ but i'll work with the suggested Plupload.

Thank you for your info anyway, I'm looking forward for any upgrades on the upload solution.
Karls

This needs to be addressed soon as Firefox will deactivate Flash by default in the very near future. Currently Chrome disables it by default and Flash is not available on iOS. Since it is a CMSB master setting, we can't have different setups for different users. It is an all or nothing. Moving to HTML5 solves this.

Please bump this up the priority list.