[
https://issues.apache.org/jira/browse/SLING-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580688#comment-13580688
]
Shashank Gupta commented on SLING-2707:
---------------------------------------
well there is overhead of appending binary in jcr node on each upload request.
It will create junk files in datastore and generate jcr events. also there is
no use of partial content in jcr.
the idea here is to store chunks in file system' temp location and merge them
on last request and create jcr node out of it. Given this implementation
context probably 200 OK for first/intermediate request and 201 CREATED
probably make more sense.
> 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
