couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Lehnardt (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-290) Include sequence number in update notifications
Date Mon, 16 Mar 2009 13:11:50 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682310#action_12682310
] 

Jan Lehnardt commented on COUCHDB-290:
--------------------------------------

@Robert Can you not simplify by not ending your loop based on the "current" seq_nr, but keep
going until no more new docs come in and then stop and wait for the next update notification
to kick off? You can then ignore all update notifications that come in while you are looping.

> Include sequence number in update notifications
> -----------------------------------------------
>
>                 Key: COUCHDB-290
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-290
>             Project: CouchDB
>          Issue Type: Improvement
>    Affects Versions: 0.9
>            Reporter: Elliot Murphy
>            Priority: Minor
>             Fix For: 0.9
>
>         Attachments: couchdb-sequences.patch, couchdb-sequences.patch
>
>
> Hi! There's been requests to include the sequence number when sending an update notification.
 Thanks to the guidance from davisp on #couchdb on March 13th, I've been able to put together
a little patch that does just that. In the future I'm interested in doing the same for the
create notification, and perhaps extending create/delete/update notifications to include a
list of affected doc IDs.
> For now though, just this simple patch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message