On Fri, Jun 7, 2013 at 3:07 AM, Benoit Chesneau <[email protected]> wrote: > Well capababilities idea come from the SMTP world at first but same > idea. That's indeed a good idea. Identification per see would't be > efficient on a client level. We don't really want to reproduce the > nightmare we have with the browsers with different U/A. Testing > capabilities is definitely a good way to test what an endpoint > support. For example some endpoint or node could only support the > replication. one ather could support the couchdb/1.3 api. other could > offers some extensions or plugin like you say. > > Though In these days I would modernize it a little as a way to > describe the api endpoints with the resource supported. > > We could base it on the host metadata rfc [1] or using some new stuffs > like the JSON api [2] . > > [1] http://tools.ietf.org/html/rfc6415 > [2] http://jsonapi.org/
I've been watching the jsonapi page and I quite like this idea.
