couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1852) Last-Event-ID header should be honoured in eventsource _changes feed
Date Wed, 28 May 2014 22:46:02 GMT


ASF subversion and git services commented on COUCHDB-1852:

Commit 002a908132bfe6a74e4a886fc539a3b7987d4c63 in couchdb-chttpd's branch refs/heads/1843-feature-bigcouch-clustered-eventsource-changes-feed
from [~gdamjan]
[;h=002a908 ]

Support Last-Event-ID header for eventsource changes feeds


> Last-Event-ID header should be honoured in eventsource _changes feed
> --------------------------------------------------------------------
>                 Key: COUCHDB-1852
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>            Reporter: Damjan Georgievski
>             Fix For: 1.4.0
>         Attachments: 0001-add-test-for-COUCHDB-1852.patch, 0002-Fix-for-COUCHDB-1852.patch
> When using the EventSource _changes feed support, the browser API will automatically
reconnect and send the last sequence it received in the Last-Event-ID header.
> The server side needs to use the Last-Event-ID instead of the 'since' query string as
a starting point for the changes feed.
> You can see the issue by simply creating a database and adding documents and watching
what happens to the eventsource _changes feed.
> To see the feed with curl use:
> {{curl -i -H 'Last-Event-ID: 2' 'http://localhost:5984/testdb/_changes?feed=eventsource'}}
> the header should also have priority over the since query string:
> {{curl -i -H 'Last-Event-ID: 2' 'http://localhost:5984/testdb/_changes?feed=eventsource?since=1'}}

This message was sent by Atlassian JIRA

View raw message