couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Smith <>
Subject Re: [PROPOSAL] Capability identification
Date Wed, 05 Jun 2013 03:45:08 GMT
On Wed, Jun 5, 2013 at 5:40 AM, Joan Touzet <> wrote:

> Today, if I GET http://localhost:5984/ , I get:
> {"couchdb":"Welcome","uuid":"b1b1dbe964914a9cb1467bfd4f297fed","version":"1.3.0","vendor":{"version":"1.3.0","name":"The
> Apache Software Foundation"}}
> If I GET from , I get:
> {"couchdb":"Welcome","uuid":"bac168113808f7ed357fb53f3a7a68bc","version":"1.3.0","vendor":{"version":"1.3.0r1","name":"Iris
> Couch"}}
> And if I GET , I get:
>   {"couchdb":"Welcome","version":"1.0.2","cloudant_build":"1202"}
> I believe I get further still different responses from Pouch and Touch
> and other CouchDB-alikes, provided they even have an equivalent of
> GET /.
> Long ago, in a galaxy far far away, the developers of Internet Relay
> Chat daemons faced a similar problem. While they were bound by a single
> RFC (and later, its twin), each developer wanted to extend the program
> in interesting and unique ways. Some of those features became
> commonplace and built a shared understanding, others were unique
> capabilities of specific implementations, and yet others indicated
> specific incompatibilities introduced for nefarious purposes.

Chris Anderson used to say, "IRC is the only network which can tolerate
netsplits. Also, it is the only network that has netsplits."


Anyway, I really like this idea. It will be easy to implement in a
federated way (everybody fleshes out their own implementation, plus central
work on ASF CouchDB). And maybe this could even encourage feature
development. Instead of a nasty "nonstandard fork" I can work on a pleasant
"new capability."

Great example:

I exercise this from probe_couchdb I don't even remember how I test for

What is the starting point? If I just brainstorm a list of potential
capabilities to this thread, does that help anybody?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message