Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Fri, 25 Jan 2013 21:53:13 +0000 (UTC)
From: "Russell Branca (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12627321.1358014485373.193161.1359150793325@arcas>
In-Reply-To: <JIRA.12627321.1358014485373@arcas>
References: <JIRA.12627321.1358014485373@arcas>
Subject: [jira] [Commented] (COUCHDB-1643) Switch to V8
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/COUCHDB-1643?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13=
563084#comment-13563084 ]=20

Russell Branca commented on COUCHDB-1643:
-----------------------------------------

Disabling I/O is definitely key to the sandbox, the real question is whethe=
r to accomplish that with a whitelist or a blacklist. I don't think there i=
s a simple way to say just disable I/O in node.js (although I haven't looke=
d into how that is accomplished in V8 either).

A view engine sandbox in my mind is an isolated execution environment that =
provides a specific set of tools for transforming a doc into a set of key/v=
alue pairs, while allowing user provided shared and side effect free code, =
that disallows any interactions with or knowledge of the underlying system =
running it.

I think the vast majority of npm modules would not be appropriate for use i=
n a view server, so I don't think free for all access to npm is the best ap=
proach for views.
               =20
> Switch to V8
> ------------
>
>                 Key: COUCHDB-1643
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1643
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: JavaScript View Server
>            Reporter: Jan Lehnardt
>
> I=E2=80=99d 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 ag=
ree 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 administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira