On 6 Jan 2009, at 12:56, Noah Slater wrote:
On Tue, Jan 06, 2009 at 12:52:26PM +0100, Jan Lehnardt wrote:
On 6 Jan 2009, at 12:43, Noah Slater wrote:
On Mon, Jan 05, 2009 at 12:54:58PM -0500, Damien Katz wrote:
For full acid commit, add a header field to the doc PUT or
_bulk_docs
POST like this:
X-Couch-Full-Commit:true
What is the cost/benefit of doing this via HTTP headers vs. query
string?
The HTTP headers way is implemented now. Damien said in another
mail, that
different options for this (per request, and db- and server-wide
config)
are on lower priority right now, but they will definitely come:
Not sure I follow. This feature is already implemented? My question
was about
the per-request way of setting this option. Should it be done using
HTTP headers
or should it be done using a query string option?
Heh, I mean: The advantage is that the header version doesn't have to be
implemented, it exists. The query-parameter version doesn't. This is
not about
the usefulness of the query-param.
I'd say the header is "more correct" because we are describing request
semantics,
not content-options. But I see arguments for the query-parameter
version as well.
Cheers
Jan
--
