[
https://issues.apache.org/jira/browse/COUCHDB-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695490#action_12695490
]
Chris Anderson commented on COUCHDB-290:
----------------------------------------
My general thought processes had been that since the db update notifier is
basically deprecated, it wouldn't hurt to start giving it a few bells and
whistles, in preparation for the making the same info available over the Comet
interface.
Damien, I take it that you're not against making the update-seq available,
you'd just rather see the db-update-notification-process go away altogether?
If now is the time to start implementing the Comet hook I guess we should start
a thread about the implementation. Eric, Elliot - I'm with Damien on thinking
this should go into the HTTP layer. I may be a little more cavalier about
playing around with the old implementation, instead of moving forward on Comet.
Damien may have a point though, that enhancing a deprecated API gives the wrong
expectations.
> 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.10
>
> 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.
