4 ms·

Shameless plug, but HTML5 + CORS + S3 can enable resumable file uploads. I've written a library that uploads to S3, and can resume uploads (think internet going

Shameless plug, but HTML5 + CORS + S3 can enable resumable file uploads. I've written a library that uploads to S3, and can resume uploads (think internet going down for a while, force-closing the tab, etc.): https://github.com/cinely/mule-uploader https://github.com/cinely/mule-uploader . There's a demo available, I suggest you test it with bigger files (>100MB)

felixge 14y ago
Your library looks great - thanks for releasing it! S3 is an incredible offering, but since I'm working on tus.io, I'll focus on what's wrong with it : ) - Multipart chunks need to be 5 MB at least. An interrupted part cannot be resumed. This kills the mobile use case. - Throughput to S3 is bad from outside of EC2, uploads often start at very slow speeds and won't reach the capacity of the connection in many cases. - S3 does not let you stream/access an upload in progress easily, so you can't start to transcode a video while it's still uploading. - The S3 API is the opposite of RESTful. - S3 is a proprietary service, their protocols are not intendent/documented for adoption, and IMO they don't deserve great people like you making free contributions to their ecosystem. edit: I'm not trying to say S3 isn't a good choice for many people. But our goal is to bring resumable file uploads to every iOS, jQuery, Wordpress, Drupal, Rails, etc. application in the world - S3 is not the right starting point for that.
- gabipurcaru 14y ago
  Thanks for your insight, you make good points; it seems to me you don't really like S3, can you elaborate why?
  - felixge 14y ago
    I love S3, and we use it all over the place at transloadit. I realized my comment sounded overly negative, so I added a clarification to my comment: Our goal is to bring resumable file uploads to the entire planet, S3 or any other proprietary protocol should not be the base for that.
    - derefr 14y ago
      What's your opinion on Swift (http://www.openstack.org/software/openstack-storage/ http://www.openstack.org/software/openstack-storage/)? It's basically an open standard for "an object store with compatibility to, and the same guarantees of, S3." Used in, for example, Rackspace Cloud Files.
- CiaranMcNulty 14y ago
  Throughput to S3 is ok if you initiate a multipart upload and then do several parallel chunk uploads.

felixge 14y ago

Your library looks great - thanks for releasing it! S3 is an incredible offering, but since I'm working on tus.io, I'll focus on what's wrong with it : ) - Multipart chunks need to be 5 MB at least. An interrupted part cannot be resumed. This kills the mobile use case. - Throughput to S3 is bad from outside of EC2, uploads often start at very slow speeds and won't reach the capacity of the connection in many cases. - S3 does not let you stream/access an upload in progress easily, so you can't start to transcode a video while it's still uploading. - The S3 API is the opposite of RESTful. - S3 is a proprietary service, their protocols are not intendent/documented for adoption, and IMO they don't deserve great people like you making free contributions to their ecosystem. edit: I'm not trying to say S3 isn't a good choice for many people. But our goal is to bring resumable file uploads to every iOS, jQuery, Wordpress, Drupal, Rails, etc. application in the world - S3 is not the right starting point for that.

gabipurcaru 14y ago
Thanks for your insight, you make good points; it seems to me you don't really like S3, can you elaborate why?
- felixge 14y ago
  I love S3, and we use it all over the place at transloadit. I realized my comment sounded overly negative, so I added a clarification to my comment: Our goal is to bring resumable file uploads to the entire planet, S3 or any other proprietary protocol should not be the base for that.
  - derefr 14y ago
    What's your opinion on Swift (http://www.openstack.org/software/openstack-storage/ http://www.openstack.org/software/openstack-storage/)? It's basically an open standard for "an object store with compatibility to, and the same guarantees of, S3." Used in, for example, Rackspace Cloud Files.
CiaranMcNulty 14y ago
Throughput to S3 is ok if you initiate a multipart upload and then do several parallel chunk uploads.