summary |
shortlog | log |
commit |
commitdiff |
tree
first ⋅ prev ⋅ next
benoitc [Sun, 16 Feb 2014 12:42:38 +0000 (13:42 +0100)]
fix undefined Req
benoitc [Sun, 16 Feb 2014 12:26:06 +0000 (13:26 +0100)]
fix handle_req
handle-req/2 was useless. Instead we wanted handle_req/1 to tell to
others which method is allowed.
benoitc [Thu, 13 Feb 2014 17:40:27 +0000 (18:40 +0100)]
fix include
benoitc [Thu, 13 Feb 2014 17:33:51 +0000 (18:33 +0100)]
remove the makefile and put a version
Dirkjan Ochtman [Wed, 7 Aug 2013 16:00:37 +0000 (18:00 +0200)]
Remove couchdb_updates files (content already in top-level LICENSE/NOTICE).
Jan Lehnardt [Mon, 4 Mar 2013 11:02:24 +0000 (12:02 +0100)]
Import couch_dbupdates from rcouch.
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.