On Mon, Jul 22, 2013 at 1:48 PM, Jan Lehnardt <[email protected]> wrote: > We have talked about deprecating features using HTTP headers like > `X-Couch-Deprecated: true` to denote a deprecation to be included in > releases that happen before the actual removal of a feature. We could > make that `X-Couch-API-Stability: [0-5]` instead, if we adopt the scale > above (and maybe only optionally show anything >0 to save some bytes > in the general case). And whatever powers that information could be > used to feed into the capabilities we have talked about for the welcome > message on `/`.
X-Couch-API-Stability idea is too complex. Better to have only `X-Couch-Deprecated: true`. Experimental features should be enabled in configs so user takes responsibility for any behavior it provides. Also, this information is useless in caps. Caps notifies what server able to do, not how good he can. -- ,,,^..^,,,
