[
https://issues.apache.org/jira/browse/COUCHDB-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Idan Zalzberg updated COUCHDB-1763:
-----------------------------------
Component/s: (was: Database Core)
HTTP Interface
> Notification changes timeout is reset on filtered changes
> ---------------------------------------------------------
>
> Key: COUCHDB-1763
> URL: https://issues.apache.org/jira/browse/COUCHDB-1763
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Reporter: Idan Zalzberg
>
> using _changes api with longpoll feed, and the 'timeout' parameter
> I also have a custom filter method that checks if the changes are relevant.
> When a change comes in that returns False on the filter method, the long
> polling does not return (as it should), but the timeout is reset.
> For example.
> if I call the _changes api with timeout 10 on time 0 it will return at time
> 10 if no changes occurred (as it should).
> However, if a change comes in at the time 5 that doesn't pass the filter
> method, the changes api will only return at time 15, leading me to believe
> that even though the change fell through the filter, the 10 sec timeout was
> somehow reset and started from 0 again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
