Re: [jira] [Commented] (COUCHDB-1367) When settings revs_limit on db - the db increases its update_seq counter when viewing stats - but not when getting changes

2011-12-27 Thread Jason Smith
On Wed, Dec 28, 2011 at 9:38 AM, Randall Leeds wrote: > On Tue, Dec 27, 2011 at 05:22, Jason Smith wrote: >> On Tue, Dec 27, 2011 at 5:04 AM, Randall Leeds >> wrote: >>> Either >>> these things have a proper place in the sequential history of a >>> database or they do not. That there are things

Re: [jira] [Commented] (COUCHDB-1367) When settings revs_limit on db - the db increases its update_seq counter when viewing stats - but not when getting changes

2011-12-27 Thread Randall Leeds
On Tue, Dec 27, 2011 at 05:22, Jason Smith wrote: > On Tue, Dec 27, 2011 at 5:04 AM, Randall Leeds > wrote: >> Either >> these things have a proper place in the sequential history of a >> database or they do not. That there are things which affect update_seq >> but do not appear in the by_seq in

[jira] [Commented] (COUCHDB-1371) configure erroneously warns against using a new spidermonkey with old spidermonkeys

2011-12-27 Thread Paul Joseph Davis (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176306#comment-13176306 ] Paul Joseph Davis commented on COUCHDB-1371: +1 > configure

[jira] [Commented] (COUCHDB-1371) configure erroneously warns against using a new spidermonkey with old spidermonkeys

2011-12-27 Thread Randall Leeds (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176280#comment-13176280 ] Randall Leeds commented on COUCHDB-1371: I hope there does come a time when we d

[jira] [Commented] (COUCHDB-1371) configure erroneously warns against using a new spidermonkey with old spidermonkeys

2011-12-27 Thread Paul Joseph Davis (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176267#comment-13176267 ] Paul Joseph Davis commented on COUCHDB-1371: While I understand your general

Re: [jira] [Commented] (COUCHDB-1367) When settings revs_limit on db - the db increases its update_seq counter when viewing stats - but not when getting changes

2011-12-27 Thread Robert Dionne
What's interesting is that modulo one edge case, last_seq in the changes feed and update_seq in the db_info record are exactly as defined on the WIKI. update_seq: Current number of updates to the database (int) last_seq: last_seq is the sequence number of the last update returned. (Currently

Re: [jira] [Commented] (COUCHDB-1367) When settings revs_limit on db - the db increases its update_seq counter when viewing stats - but not when getting changes

2011-12-27 Thread Jason Smith
On Tue, Dec 27, 2011 at 5:04 AM, Randall Leeds wrote: > Yes it does. There is mostly consistent relationship between update > sequence (seq, update_seq, last_seq, committed_seq) and the by_seq > index. It seems entirely too confusing that there are things which > affect update_seq but do not appea

Re: browserid support

2011-12-27 Thread Jason Smith
On Tue, Dec 27, 2011 at 8:45 AM, Benoit Chesneau wrote: > Current implementation of browserid is worthless imo Indeed. > It's good to show how it could work, Cue Inigo Montoya. -- Iris Couch

Re: browserid support

2011-12-27 Thread Benoit Chesneau
On Tue, Dec 27, 2011 at 6:09 AM, Randall Leeds wrote: > On Sun, Dec 25, 2011 at 22:02, Jason Smith wrote: >> On Mon, Dec 26, 2011 at 9:51 AM, Michiel de Jong >> wrote: >>> The other thing, CouchDB as a BrowserId RP, would simply be instead of >>> clicking 'login' at the bottom right in futon, t