You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Chris Anderson (JIRA)" <ji...@apache.org> on 2010/02/12 07:21:27 UTC
[jira] Commented: (COUCHDB-650) Add "now" option for ?since
parameter on _changes
[ https://issues.apache.org/jira/browse/COUCHDB-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832859#action_12832859 ]
Chris Anderson commented on COUCHDB-650:
----------------------------------------
The problem with since=now is that it can lead to missed updates.
There should be a ticket to make view responses include the view_seq and to expose doc._local_seq via a GET parameter.
It's much better to know what seq your state is current as of, than to miss updates.
> Add "now" option for ?since parameter on _changes
> -------------------------------------------------
>
> Key: COUCHDB-650
> URL: https://issues.apache.org/jira/browse/COUCHDB-650
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface
> Reporter: Randall Leeds
> Priority: Minor
> Attachments: 0001-add-since-now-option-to-continuous-catch-edge-cases-.patch
>
>
> As per a discussion on IRC with mikeal, jan_____, whartung, and rnewson:
> Having _changes?since="now" allows clients to listen to only new changes without making two requests (one to extract seq from /db, and one _changes).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.