[
https://issues.apache.org/jira/browse/COUCHDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332294#comment-14332294
]
Sebastian Podjasek commented on COUCHDB-1779:
---------------------------------------------
I've suggested using PATCH method (http://tools.ietf.org/html/rfc5789). To be
honest RFC says nothing about Content-* or Range headers, it suggest using a
"patch document" from request body.
IMHO using of some request header would be simpler to implement from client
side (just as it works with Amazon's Glacier Multipart uploads).
> Support of HTTP PATCH method to upload/update attachments in chunks
> -------------------------------------------------------------------
>
> Key: COUCHDB-1779
> URL: https://issues.apache.org/jira/browse/COUCHDB-1779
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core, HTTP Interface
> Reporter: Sebastian Podjasek
> Priority: Minor
>
> I'm wondering would it be possible to implement PATCH methods for document
> attachments.
> I'm currently facing a theoretical problem to upload large files over GSM
> network, my storage back-end is CouchDB with our own API served in front-end.
> I was thinking about few other solutions, but all of them involves some post
> processing of document after receiving last chunk, it would be great to just
> invoke this:
> PATCH
> /database/0519690fc465fc0e9cc0f89fa87973fc/bigfile.dat?_rev=13-c969cb72e5428ca2ccdd191e0cd7bf4b
> HTTP/1.1
> Content-Type: application/octet-string
> Range: bytes=1200-1300
> Content-Length: 100
> What do you think about this. Is it theoretically possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
