[
https://issues.apache.org/jira/browse/SLING-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559556#comment-13559556
]
Shashank Gupta commented on SLING-2707:
---------------------------------------
> 1) The upload requests should return 201, not 200.
First/Intermediate upload does create any resource so 200 should be fine. Last
chunk upload does the actual creation which returns 201.
>2) The GET on an unknown upload should return a 4xx status code, not a 5xx.
>Probably simply 404.
ok will correct.
>3) The "Location" response header field on "Get last successful upload chunk
>response" looks fishy. What is it for? Doesn't the information belong into the
>payload?
it is not required.will correct
>Also: do we absolutely need the ".html" in the request URI?
iirc, for a non existing resource, if i don't specify extension, selector is
used as extension. so in that sense it is required. I will recheck.
> 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
