From dev-return-25041-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Thu Jan 31 15:40:28 2013 Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A8C98E06B for ; Thu, 31 Jan 2013 15:40:28 +0000 (UTC) Received: (qmail 75370 invoked by uid 500); 31 Jan 2013 15:40:28 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 75343 invoked by uid 500); 31 Jan 2013 15:40:28 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 75331 invoked by uid 99); 31 Jan 2013 15:40:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2013 15:40:27 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [80.244.253.218] (HELO mail.traeumt.net) (80.244.253.218) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2013 15:40:21 +0000 Received: from [10.0.0.27] (91-66-82-235-dynip.superkabel.de [91.66.82.235]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.traeumt.net (Postfix) with ESMTPSA id 245F8143D0 for ; Thu, 31 Jan 2013 16:35:36 +0100 (CET) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: Branch to switch from SpiderMonkey to Node.js From: Jan Lehnardt In-Reply-To: Date: Thu, 31 Jan 2013 16:39:59 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <91019D9B-A6AE-4311-9C11-E6001D57293A@apache.org> References: <5102B439.10500@lymegreen.co.uk> To: dev@couchdb.apache.org X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org On Jan 31, 2013, at 16:26 , Benoit Chesneau wrote: > On Thu, Jan 31, 2013 at 4:16 PM, Jason Smith = wrote: >=20 >>=20 >>=20 >> Yes this is the problem. You are right. This is Jan's answer. CouchDB = is >> already resilient to a few different runtimes. >>=20 >> - having more concurrency for couchapps and view indexation >>>=20 >>=20 >> Love it, but out of scope in this thread. >>=20 >>=20 >>>=20 >>> Imo one of these problems can be solved by improving the view = protocole. >> I >>> think we could work on a new protocole. And while we are here really >>> document the current one as a specification in text. >>>=20 >>=20 >> Love it, but of scope in this thread. >>=20 >=20 >=20 > But if we change the view server, we should also think about it. For > example the implementation of couchjs in node is using fibers and try = to > add some concurrency on a protocol (stdin/stdout) that isn't . Where = if we > go to TCP or UNIX sockets we have natural system concurrency. I am = not > sure anyway why fibers are used there if it's not about pseudo = concurrency. We should absolutely innovate on the view server, I just don=92t see it happen as-is. As per the last mail, if we open this up to an community that cares about this a lot, we can only win without doing much work ourselves. I don=92t see how this is not the obvious thing to do. >> But what is your "problem" to solve? If you are talking about speed = and >> concurrency and stuff, I think that is a 2.x discussion. >>=20 >=20 > i'm speaking about easing the distribution of couchdb on a big = deployment > Using v8 would allows me to build it statically and embed it in an = erlang > release. The other advantage compared node is that I won't have to = make > sure that nodejs is still running, not idling etc. In other word it = would > reduce the stack. Why can=92t we embed node with v8 into Erlang? That is totally something = I want to go towards. I just don=92t want to overcomplicate things and = make the query-server model work first. The embedding then can be an = optimisation. >=20 >=20 >>=20 >> Can someone please specifically describe a "sandbox" feature? CouchJS >> passes the test suite. So what does the sandbox do? >>=20 >=20 > did it many time. See my other mail where I tried to summarise it = again. Can you give me a link? I was rather busy with CouchDB Conf prep in the past weeks. Cheers Jan --=20