Document new options, remove obsolete ones.
Document custom HTTP/socket options in default.ini
Part of the backport of COUCHDB-1008 to chttpd. This just updates
the default.ini with some commented out options describing their
availability to users.
If we continue to support the dedicated [chttpd] backlog parameter we should remove backlog from the example config, as the current implementation in chttpd will always ignore it.
I wasn't entirely certain on the best approach. In a perfect world I'd like to drop backlog but I wouldn't want people to get confused. Perhaps a warning/error if it's set and then document it in the release notes?
+1 on removing [chttpd] backlog. You could write a one-liner explaining it moved to the options section immediately below it.
Fine by me if we remove backlog from the top-level chttpd options.
Remove obsolete options, document N,Q
Ok, I removed [chttpd] backlog, [httpd] max_connections (it's a noop in the current mochiweb), and replaced os_process_limit with os_process_soft_limit in [query_server_config (we use a different process manager than vanilla CouchDB). I'd like to clean it further some day but I don't want to hold up the release candidate for it.
I also removed the duplicate documentation of server_options and socket_options in [httpd]. Anyone tweaking those settings for the backend interface is Doing It Wrong.