Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <66f535320804150830g362d7a23l74270f00da6f21ce@mail.gmail.com>
Date: Tue, 15 Apr 2008 17:30:12 +0200
From: "Oliver Oli" <oliver.oli+0815@gmail.com>
Sender: oli@streaps.org
To: couchdb-user@incubator.apache.org
Subject: Re: Posting an attachment directly
In-Reply-To: <41fe564f0804141613y37f638bdi350ec65d2cb79ffb@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <41fe564f0804141613y37f638bdi350ec65d2cb79ffb@mail.gmail.com>

I also would like to see direct binary attachement upload as an
alternative to the base64 encoded attachements. why waste cpu cycles?

On Tue, Apr 15, 2008 at 1:13 AM, Ralf Nieuwenhuijsen
<ralf.nieuwenhuijsen@gmail.com> wrote:
> Hi, i'm tempting to go an all javascript route interfacing with couchdb.
>  (i'm using qooxdoo)
>
>  But two potentional aspects worry me:
>
>  1. Will it be supported in the future to post an attachment directly?
>  This would make it possible ot use the browser to directly upload a file to
>  the couchdb server
>
>  POST /somedatabase/somedoc/_attachment HTTP/1.0    <== adds a new attachment
>
>  2. Will it be possible to use allow a post alternative for put & delete
>  operations?
>  This would enable crossdomain usage using an iframe backend ;-)
>
>  POST /somedatabase/_bulk_docs   HTTP/1.0         <== put alternative
>  already exists!
>  POST /somedatabase/_bulk_delete HTTP/1.0         <== delete
>  alternative doesn't exist yet!
>
>  PS. Do we delete attachment by just removing them from the document?
>
>  Greetings,
>  Ralf
>
>
>   -
>
>  This was a browser can be used to post attachments directly to the couchdb
>  server.
>