[ 
https://issues.apache.org/jira/browse/COUCHDB-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168065#comment-13168065
 ] 

Paul Joseph Davis commented on COUCHDB-1362:
--------------------------------------------

Except sealing has issues in some versions. And I'm not sure if that even gets 
us out of crazy town. We already use sub-contexts that are sealed if possible 
and I'm not entirely certain on the interplay there. I've also heard from other 
SpiderMonkey embeders that do things like "scan k/v pairs on global, run js, 
delete unknown keys and reset values" which sounds like a best effort but not 
full proof way of dealing with this.

Basically, there's a lot to this and "don't do that" has served us well enough 
for long enough that unless someone wants to take on the task of making these 
things work for our supported versions of SpiderMonkey I'd be a bit hesitant on 
allocating cycles to it right now.
                
> couchjs doesn't clean out global namespace between views calls
> --------------------------------------------------------------
>
>                 Key: COUCHDB-1362
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1362
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 1.1.1
>         Environment: Linux
>            Reporter: jay groven
>            Priority: Minor
>
> Sometimes a view can access the functions that were defined in a previous 
> view.  This can lead a developer to think that function sharing has been 
> implemented, but it's not reliable behaviour.  It would be better if the 
> global namespace were cleared between map/reduce runs so that it's clear that 
> there is no reliable way to share functions between views.

--
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

        

Reply via email to