[
https://issues.apache.org/jira/browse/SLING-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559660#comment-13559660
]
Julian Reschke commented on SLING-2707:
---------------------------------------
> 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/
The point being that any chunk you upload *is* a temporary resource, and
there's no reason why a GET on it's URI should return the content with status
code 200. With respect to 206: the relevant specs are RFC 2616 and
http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p5-range-latest.html for
the latest&greatest...
> 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
