[
https://issues.apache.org/jira/browse/COUCHDB-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182312#comment-15182312
]
Alexander Shorin commented on COUCHDB-2964:
-------------------------------------------
I thought about all of this for a while and have another question: how
"longpoll" is different from continuous feed with non-infinity timeout? Now
"longpoll" inherited this option, but it makes no sense for it.
The question about "normal" vs "longpoll" is about "Do we want to keep a
connection listening for the changes, or spawn it eventually all the time to
ask if something had changed". I think it's quite strange to fallback into HTTP
1.0 times today.
> Investigate switching replicator manager change feeds to using "normal"
> instead of "longpoll"
> ---------------------------------------------------------------------------------------------
>
> Key: COUCHDB-2964
> URL: https://issues.apache.org/jira/browse/COUCHDB-2964
> Project: CouchDB
> Issue Type: Improvement
> Components: Replication
> Reporter: Nick Vatamaniuc
> Assignee: Nick Vatamaniuc
> Fix For: 2.1
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
