Honestly this sounds like a good job for OPTIONS but Mark Nottingham would
disagree - see http://www.mnot.net/blog/2012/10/29/NO_OPTIONS. Personally I
think a Couch DB specific solution (e.g. returning server data as JSON on a GET
request on the root of the server) is just fine. Good general purpose solutions
are hard. Good specific solutions tend to be easier.
Yaron
Sent from Windows Mail
From: Jens Alfke<mailto:[email protected]>
Sent: Wednesday, February 5, 2014 7:20 PM
To: [email protected]<mailto:[email protected]>
On Feb 5, 2014, at 5:22 PM, Klaus Trainer <[email protected]> wrote:
> Regarding your example about trying to find out if a _bulk_get feature
> is available, this is what you could do: check if the
> "httpd_db_handlers" object has a "_bulk_get" property. If yes, it means
> that there is a handler for "/:db/_bulk_get" queries.
That seems rather CouchDB-specific. What I'm talking about is something that
would work with any API-compatible implementation, including ones that are
architecturally quite different.
—Jens
