On 26 Feb 2009, at 18:43, Jens Alfke wrote:
[This is in response to "(COUCHDB-269) _list doesn't allow POST
requests", but I'm posting to the list as the issue seems to be
broader than just the _list URI pattern.]
Using POST to fetch documents seems a bit weird — by REST principles
that should be a GET, shouldn't it? Using a POST obscures the fact
that the request is read-only and potentially cacheable. Any reason
this couldn't be handled by a GET, passing in the document IDs?
Is it the potential size of the resulting URI?
Yes.
(Is it kosher to pass a request body in a GET?)
The RFC allows it, but it is not widely supported.
This came up before on the dev list, but I don't blame you because
the incubator archives seem to be gone.
Cheers
Jan
--
