[jira] Resolved: (COUCHDB-650) Add "now" option for ?since parameter on _changes

["Chris Anderson (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/COUCHDB-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Anderson resolved COUCHDB-650.
------------------------------------

    Resolution: Fixed

This is mostly closed by r931439 (Thanks Joscha)

r931439 adds an update_seq JSON member to view responses, making it possible to use _changes to update information loaded via view, without chances of getting multiple updates twice, or missing updates.

This doesn't add a ?local_seq=true option to document requests, but if anyone wants to add this, it would be the way to go (similar to the ddoc.options.local_seq = true that can be used to make the doc._local_seq available to the view engine.)

> 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, update_seq.diff, view_update_seq.js
>
>
> 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.