While I tried to land COUCHDB-1432 on 1..x.x it turned out that /benches/run is broken in several places for a longer time and nobody noticed: When trying to fix it (adding a file called test_setup.js) to the template, we will get the next error. As nobody noticed that it is broken for a longer time it seems we currently have no need for benchmarks, and if we have that need, we should add new ones which reflect our current needs and are compatible with 2.0 too. This removes the leftovers of the benchmark which is also broken on 1.6.x for a longer, unknown time which was already deleted in parts for 2.0
This creates a new top level API endpoint: `/_db_updates` that returns a line of JSON for each database event along with the database name. A database event is one of `created`, `updated`, `deleted`. The API endpoint supports a `?feed=` parameter with the options: `longpoll`, `continuous` and `eventsource`. A second parameter `timeout=` specifies when the server should close the connection. `longpoll` closes the connection after a single notification. It is the default option. `continuous` keeps a socket open until the specified `timeout` or 60 seconds by default. `heartbeat` decides whether to send a newline character on `timeout` to avoid clients closing the connection prematurely. `eventsource` works like continuous, but sends the data in EventSource format. See http://dev.w3.org/html5/eventsource/ The parameters are modelled after the existing `/_changes` API endpoint. Note that `/_db_updates` does not support resuming of notifications via a sequence ID. This is a port of the existing DbUpdateNotification interface to the HTTP API. Functional changes compared to rcouch: - make _db_updates an admin-only resource Docs: - updated api/misc to include basic info on `/_db_updates` License: Apache 2 license, updated LICENSE. Notice: (c) 2012 Benoit Chesneau, updated NOTICE. Tests: - only manual testing of the various API differences due to complications with asynchronous HTTP requests in the JS test suite and total annoyance of overly complicated ibrowse/httpc modules for writing etap tests. Recommendation to ship this as EXPERIMENTAL until we have tests.