[ 
https://issues.apache.org/jira/browse/SLING-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581294#comment-13581294
 ] 

Alexander Klimetschek commented on SLING-2707:
----------------------------------------------

> Introducing a new node type sling:PartialFile seems unnecessary complexity

Ok, the implementation specifics can be discussed separately.

> Current spec with part number gives opportunity for future extension for 
> supporting uploading of parallel chunks

My proposal using the sling post servlet and @RangeStart/End allows for the 
same; it might be necessary to (initially) include the full file size (e.g. 
@FileLength) as well, so the server side knows when it is finished and can 
assemble the final file.

Regarding S3: as Ian mentioned, the use case for their chunks was different 
than the resumable upload we are discussing here. So it should not really 
dominate how our solution should look like. And IMHO it's quite intuitive to 
follow the Range concept of HTTP GETs - byte ranges are more flexible and 
self-describing than a fixed number of chunks. The only thing is that we can't 
use the Range headers directly as it's not spec compliant to reuse that header 
for PUT/POST/PATCH and we don't want to introduce a proprietary header (X-* 
considered harmful). Finally, having the chunk number in the URL is just 
complicating things - the sling post servlet feels like a natural place to add 
this feature to.
                
> 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

Reply via email to