[jira] [Updated] (COUCHDB-1116) Documentation for jquery.couch.js
[ https://issues.apache.org/jira/browse/COUCHDB-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-1116: - Attachment: jquery.couch.js-docs.patch > Documentation for jquery.couch.js > - > > Key: COUCHDB-1116 > URL: https://issues.apache.org/jira/browse/COUCHDB-1116 > Project: CouchDB > Issue Type: Improvement > Components: Documentation >Reporter: Dale Harvey >Priority: Minor > Attachments: jquery.couch.js-docs.patch > > > Creating documentation for jquery.couch.js -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1116) Documentation for jquery.couch.js
Documentation for jquery.couch.js - Key: COUCHDB-1116 URL: https://issues.apache.org/jira/browse/COUCHDB-1116 Project: CouchDB Issue Type: Improvement Components: Documentation Reporter: Dale Harvey Priority: Minor Attachments: jquery.couch.js-docs.patch Creating documentation for jquery.couch.js -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: SpiderMonkey 1.8.5 upgrades
On Apr 1, 2011, at 7:26 PM, Paul Davis wrote: > Hey, > > Mozilla released a SM 1.8.5 source distribution this morning [1]. > We've been getting requests from various places to upgrade our couchjs > to use this newer version for a couple weeks and now that its > available, there's no better time to act. > > As can be expected, this new SpiderMonkey has a fairly significant API > change from what we've been using in couchjs. Up until now we've been > able to get away with supporting 1.7 and the 1.8.0rc1 tarballs without > much hassle. The new API makes this much more difficult. Chris C > Coulson from Ubuntu has been working on a patch that'll allow us to > work with 1.8.5 and (IIRC) should work with the 1.8.0rc1 but it > includes some extra gnarly ifdef magic to make things work. > > So my question is what versions of SM should we support? I would > probably vote to drop everything in favor of 1.8.5 and no longer > support the older APIs. There is a possibility of just having two > versions of couchjs that we choose at compile time. But from what I've > heard and seen, we're basically not going to be able to have a single > compile time ifdef decision on versions without some super screw code. > > Thoughts? > > [1] http://ftp.mozilla.org/pub/mozilla.org/js/ Well, we need to continue to support SM 1.7 on the 1.0.x branch, and if that means 1.0.x doesn't work with SM 1.8.5 then so be it. For 1.1.0 I'd want to know what the availability of SM 1.8.5 in various package repositories looks like before dropping support for SM 1.7. Ideally I'd like to ship at least one version of CouchDB that works with both SM 1.7 and SM 1.8.5, but I've seen Chris' work in COUCHDB-1078 and I don't relish the thought of making that any more complicated than it already is. Trunk can drop support for SM 1.7. Adam
SpiderMonkey 1.8.5 upgrades
Hey, Mozilla released a SM 1.8.5 source distribution this morning [1]. We've been getting requests from various places to upgrade our couchjs to use this newer version for a couple weeks and now that its available, there's no better time to act. As can be expected, this new SpiderMonkey has a fairly significant API change from what we've been using in couchjs. Up until now we've been able to get away with supporting 1.7 and the 1.8.0rc1 tarballs without much hassle. The new API makes this much more difficult. Chris C Coulson from Ubuntu has been working on a patch that'll allow us to work with 1.8.5 and (IIRC) should work with the 1.8.0rc1 but it includes some extra gnarly ifdef magic to make things work. So my question is what versions of SM should we support? I would probably vote to drop everything in favor of 1.8.5 and no longer support the older APIs. There is a possibility of just having two versions of couchjs that we choose at compile time. But from what I've heard and seen, we're basically not going to be able to have a single compile time ifdef decision on versions without some super screw code. Thoughts? [1] http://ftp.mozilla.org/pub/mozilla.org/js/
[jira] [Commented] (COUCHDB-1115) Added button to cancel continuous replications
[ https://issues.apache.org/jira/browse/COUCHDB-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014537#comment-13014537 ] Egbert Teeselink commented on COUCHDB-1115: --- Btw, if applied together with https://issues.apache.org/jira/browse/COUCHDB-1016 the code can be simplified by using $.couch.replicate() instead of jQuery.ajax(). > Added button to cancel continuous replications > -- > > Key: COUCHDB-1115 > URL: https://issues.apache.org/jira/browse/COUCHDB-1115 > Project: CouchDB > Issue Type: Improvement > Components: Futon >Reporter: Egbert Teeselink >Priority: Minor > Labels: cancel, javascript, replication > > In response to a challenge from Jan Lehnart during the Berlin CouchDB > training, I added a "cancel" link to the status page of Futon, so that > running continuous replications can be cancelled. > It can only cancel "vanilla" continuous replications, so ones that use filter > functions or create_target will not work. I understood from Jan that this is > fine, because later CouchDB versions will have sessions addressable as > resources. Until then, this patch can cancel the continuous replications that > Futon allows you to start. > I wanted to try out github, so I forked and committed: > https://github.com/eteeselink/couchdb/commit/e3295ed0d24b221206ef0f1cf75f78946297db31 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1115) Added button to cancel continuous replications
Added button to cancel continuous replications -- Key: COUCHDB-1115 URL: https://issues.apache.org/jira/browse/COUCHDB-1115 Project: CouchDB Issue Type: Improvement Components: Futon Reporter: Egbert Teeselink Priority: Minor In response to a challenge from Jan Lehnart during the Berlin CouchDB training, I added a "cancel" link to the status page of Futon, so that running continuous replications can be cancelled. It can only cancel "vanilla" continuous replications, so ones that use filter functions or create_target will not work. I understood from Jan that this is fine, because later CouchDB versions will have sessions addressable as resources. Until then, this patch can cancel the continuous replications that Futon allows you to start. I wanted to try out github, so I forked and committed: https://github.com/eteeselink/couchdb/commit/e3295ed0d24b221206ef0f1cf75f78946297db31 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
