couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Smith (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1643) Switch to V8
Date Thu, 17 Jan 2013 12:54:23 GMT


Jason Smith commented on COUCHDB-1643:

Do we port couchjs to V8, or do we write a new Node.js couchjs? Is that the basic question
of this ticket?

I would like to hear people's definition of the "sandbox." What exactly are its features?

I will start:

1. Code from one design document has no way to affect code from another. Global variables
do not persist, etc.
2. There is no way to perform i/o from the JavaScript process

My basic feeling is, this is easier to do in Node than embedded V8.

Yes, embedded V8 is more pure and you have more control; however the Node.js ecosystem is
simply so gigantic, and growing. It is more likely that Node can provide what we need.

For example, the view server (share/server/*.js) expects a synchronous readline() function.
I was able to build that trivially using the fibers package Tools to help with security/sandboxing
are probably out there already too.
> Switch to V8
> ------------
>                 Key: COUCHDB-1643
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: JavaScript View Server
>            Reporter: Jan Lehnardt
> I’d like to propose that we switch to the V8 JavaScript engine to mitigate the various
issues we have with SpiderMonkey.
> This ticket acts as the meta-issue where we can discuss whether we all agree and what
needs doing. individual tasks then can get their own tickets.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message