Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Fri, 26 Apr 2013 08:24:15 +0000 (UTC)
From: "Robert Newson (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12644783.1366959699939.230375.1366964655837@arcas>
In-Reply-To: <JIRA.12644783.1366959699939@arcas>
References: <JIRA.12644783.1366959699939@arcas>
Subject: [jira] [Commented] (COUCHDB-1779) Support of HTTP PATCH method to
 upload/update attachments in chunks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Newson commented on COUCHDB-1779:
----------------------------------------

It's possible at the database level to add chunks of attachments separately, the question is what the API looks like that's also RFC 2616 kosher, and then it's just a question of developer time and priority.
                
> 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 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