[jira] [Commented] (COUCHDB-1302) Fix couchjs

2011-10-12 Thread Randall Leeds (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/COUCHDB-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13125637#comment-13125637
 ] 

Randall Leeds commented on COUCHDB-1302:


Tested 1.1.x with Paul's patches applied. I checked it against a few 
spidermonkey versions including debian unstable from the iceweasel package, 
ubuntu's xulrunner-1.9.2.17-dev and libmozjs185-dev. Verified that the 
configure throws an error on the new one. Didn't check spidermonkey trunk, but 
I trust that patch 0002 is fine. I say commit it for 1.1.x and we can start the 
release process, then open a new ticket to talk about what to do about 1.2.

Thanks, Paul!

 Fix couchjs
 ---

 Key: COUCHDB-1302
 URL: https://issues.apache.org/jira/browse/COUCHDB-1302
 Project: CouchDB
  Issue Type: Improvement
  Components: JavaScript View Server
Affects Versions: 1.1.1, 1.2, 1.3
Reporter: Paul Joseph Davis
Priority: Blocker
 Attachments: 
 0001-Prevent-linking-against-too-new-of-a-SpiderMonkey.patch, 
 0002-Minor-fixes-to-link-agianst-SpiderMonkey-trunk.patch


 Figure out why some spidermonkeys have an error when doing: 
 eval(function(){})

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (COUCHDB-1289) heartbeats skipped when continuous changes feed filter function produces no results

2011-10-12 Thread Bob Dionne (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/COUCHDB-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bob Dionne updated COUCHDB-1289:


Attachment: 0001-Ensure-heartbeats-are-not-skipped-in-continuous-chan.patch

This patch against current master fixes the heartbeat issue

 heartbeats skipped when continuous changes feed filter function produces no 
 results
 ---

 Key: COUCHDB-1289
 URL: https://issues.apache.org/jira/browse/COUCHDB-1289
 Project: CouchDB
  Issue Type: Bug
  Components: Database Core
Reporter: Bob Dionne
Assignee: Bob Dionne
Priority: Minor
 Attachments: 
 0001-Ensure-heartbeats-are-not-skipped-in-continuous-chan.patch


 if the changes feed has a filter function that produces no results, 
 db_updated messages will still be sent and the heartbeat timeout will never 
 be reached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (COUCHDB-1304) set Expires header on session cookies to make them persistent

2011-10-12 Thread max ogden (Created) (JIRA) 
set Expires header on session cookies to make them persistent
-

 Key: COUCHDB-1304
 URL: https://issues.apache.org/jira/browse/COUCHDB-1304
 Project: CouchDB
  Issue Type: Improvement
  Components: HTTP Interface
Affects Versions: 1.1
Reporter: max ogden
Priority: Minor
 Fix For: 1.1


currently couch's cookie based authentication only sets session cookies as 
opposed to persistent cookies. the difference between these two is the Expires 
header. if it is not present most web browsers will delete your cookie when you 
quit your browser, whereas if it is set then your browser keeps the cookie 
around until the time specified by the Expires header.

This sucks for UX because users quit and re-launch their browser they'll have 
to log in again. 

I am proposing that we set the Expires header in cookies to match the time in 
the couch_httpd_auth timeout

p.s. this is similar to the issue I opened 
https://issues.apache.org/jira/browse/COUCHDB-1095 but at that time I didn't 
realize that what I really wanted was the Expires header

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira