[
https://issues.apache.org/jira/browse/COUCHDB-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194030#comment-14194030
]
Joan Touzet commented on COUCHDB-2237:
--------------------------------------
I'm -0.9 on this suggestion. "Live" implies that changes are instantaneously
sent, which isn't necessarily true. First off, without a since value it'll
start from the earliest rev it knows of, which certainly isn't "live" data. And
even if you are "caught up" in the feed, there are still reasons why the feed
you get will not be near-instantaneous, especially if someone else is
replicating (old?) documents into the db, or if you're in a degraded cluster
that is suddenly rejoined together (similar to the replication scenario).
TL;DR: "live" might be easier to type than "continuous" but it doesn't mean the
same thing.
> Add a 'live' sugar for 'continuous'
> -----------------------------------
>
> Key: COUCHDB-2237
> URL: https://issues.apache.org/jira/browse/COUCHDB-2237
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: HTTP Interface
> Reporter: Dale Harvey
>
> With PouchDB we generally try to stick to the same param names as Couch, we
> are even changing some we implemented first to be compatible
> (https://github.com/pouchdb/pouchdb/issues/2193)
> However 'continuous' sucks to type, its confusing to type and spell and
> everyone gets it wrong, we still support it but switched to documenting it as
> 'live' and life is awesome again
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
