Github user nickva commented on the issue:
https://github.com/apache/couchdb-chttpd/pull/144
@kxepal It probably can be used to build the list of features, maybe with
some feature discover- ability API extension. Or maybe it can override
get_features().
So far I left it simple as a start.
To provide more context for this, for example Cloudant uses something like
this for the geo code. Users can tell if it is enabled or not.
We just had another usage example: the new replicator code (you might have
seen it in the "next" CouchDB mailing list). It improves a few things, but in
doing so it changes the API a bit so docs don't get all the state updates
written back to them. This would allow for example for user code to quickly
check if the new replicator is loaded (to know not to expect "triggered" states
in replication docs). I imagine some might prefer to user one replicator vs the
other for a while to maintain backwards compatibility.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
