You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Benoit Chesneau (JIRA)" <ji...@apache.org> on 2012/06/22 17:54:44 UTC
[jira] [Updated] (COUCHDB-1501) Add flag to the changes API to
return only new changes
[ https://issues.apache.org/jira/browse/COUCHDB-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Chesneau updated COUCHDB-1501:
-------------------------------------
Skill Level: New Contributors Level (Easy)
Labels: changes http (was: )
> Add flag to the changes API to return only new changes
> ------------------------------------------------------
>
> Key: COUCHDB-1501
> URL: https://issues.apache.org/jira/browse/COUCHDB-1501
> Project: CouchDB
> Issue Type: New Feature
> Components: JavaScript View Server
> Affects Versions: 1.2
> Reporter: Daniel Gonzalez
> Priority: Minor
> Labels: changes, http
>
> As discussed in this thread: http://mail-archives.apache.org/mod_mbox/couchdb-user/201206.mbox/%3CCAAOi-OHB6%3DYu%2Bt%3DWkiFAypQAfnv%3DQd-PL4tELZNL1C1-TQvtWw%40mail.gmail.com%3E
> I copy paste part of the conversation.
> ---
> I am subscribing to the _changes API. My database is quite big, and each time I restart my client, I get all old notifications. I only need the new notifications, since the moment that I subscribe to the feed.
> I have seen that there is a "since" parameter, but this is not helping me further, because I do not know what is the last document sequence number. So I would need one of the following:
> - a method to get the last sequence number to use as value for "since"
> - a flag to tell the _changes API to just give me the changed *from now on*. This would be the most clean solution, since it saves me a request to get the since parameter (which can be outdated anyway very fast). Is there something like this?
> ---
> I ended up going the GET /dbname route
> I guess there is no specific flag for the _changes API to request future changes...
> ---
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira