[
https://issues.apache.org/jira/browse/SLING-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559651#comment-13559651
]
Shashank Gupta commented on SLING-2707:
---------------------------------------
> Well, it does create a resource, just not the final resource.
Till the last chunk gets uploaded, the subsequent GET call to the url will
return 404 so 201 doesn't looks correct to me. 206 looks more appropriate but
it is restricted to GET.
http://benramsey.com/blog/2008/05/206-partial-content-and-range-requests/
>I wonder if you couldn't do range uploads instead of chunks?
The reason we are not doing range uploads because sling endpoint won't be
extensible to support parallel chunk upload. As go on range based upload, the
chunk can vary in size and it would be impossible to handle out of sequence
chunk arrival. Probably the reason Amazon aws uses chunk numbers
http://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html.
> AFAICS, this should also be possible in a (modern) browser, using
> Blob.slice() from the html5 File API....
Yes I agree. imo, OPTIONS http://<slingserver>:<port> should tell client
whether sling support chunk upload. I am investigating ways to support that.
The other approach can be all html5 based browser do chunked upload and rest do
plain upload.
Any other idea is welcomed here?
> And avoid action verbs like "upload" in the URL... but as noted above, no
> selector should be necessary at all.
Not sure i get it. how request will hit my endpoint if don't specify selector.
>POST /content/dam/dam-folder/asset.pdf.chunk.2.html
[chunk, 2 ] are selector here. correct ?
> Then there is no need to manage chunks on the server side, you only need to
> append to an existing binary. Also it's all in the spec already AFAICS, no
> need to invent a custom scheme
implementation detail. for extensible parallel connection design/protocol, it
require to keep chunks temporary.
> Support of chunked file upload into Sling
> -----------------------------------------
>
> Key: SLING-2707
> URL: https://issues.apache.org/jira/browse/SLING-2707
> Project: Sling
> Issue Type: New Feature
> Components: General
> Reporter: Shashank Gupta
> Attachments: uploadclient.jar
>
>
> Use cases:
> 1. Large file upload - With high speed internet connections, advent of cloud
> and HD going mainstream, Sling should support large files (> 2GB) upload.
> 2. Fault tolerant uploads - Sling should provide capability to resume upload
> from failure point. It should not require client to restart the complete
> upload process.
> 3. Faster upload: Sling should support its clients to initiate multiple
> connection and upload file chunks in parallel.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
