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 C41C2E397 for ; Thu, 31 Jan 2013 15:27:25 +0000 (UTC) Received: (qmail 35542 invoked by uid 500); 31 Jan 2013 15:27:25 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 35381 invoked by uid 500); 31 Jan 2013 15:27:25 -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 35360 invoked by uid 99); 31 Jan 2013 15:27:24 -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:27:24 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bchesneau@gmail.com designates 209.85.210.174 as permitted sender) Received: from [209.85.210.174] (HELO mail-ia0-f174.google.com) (209.85.210.174) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2013 15:27:19 +0000 Received: by mail-ia0-f174.google.com with SMTP id o25so4026039iad.33 for ; Thu, 31 Jan 2013 07:26:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=zW7ViGgfMNvkYTmt4TAXtdLu3Qiix1oD0b4M7zHh2LQ=; b=l0yWL0eZOnBhzBqmYI+0ZVjyoOeBmXy4kAXAIUMIy0kjzgmH9hWBp9yS7FSodE0SHy rgUYMTycaYWrFO9h0UNwudXV37nMb0UE/M9PE7ExE1reAWjccsvAvyy/NCXNBtMRJ/a7 cpEkOzBPX9uVok11gsrplST22+7NgcqKLCdtACHY31d6aZfG/bLotN/F/2sKczZOB51s VIPku7pPMW2NGaA3cBZyxRQjl3WFoYkzcPCS1YKtVMBar7rX30tnpkeqD3/mb/Wfob+T Z3egEJZfGUDAy0a44Hmaib5HcqVdRDctDgTDhWht4LdAdHd9Ar/4K35JU1bD0Ypd5eK6 B5oQ== MIME-Version: 1.0 X-Received: by 10.50.222.232 with SMTP id qp8mr1479604igc.25.1359646018798; Thu, 31 Jan 2013 07:26:58 -0800 (PST) Received: by 10.64.29.13 with HTTP; Thu, 31 Jan 2013 07:26:58 -0800 (PST) In-Reply-To: References: <5102B439.10500@lymegreen.co.uk> Date: Thu, 31 Jan 2013 16:26:58 +0100 Message-ID: Subject: Re: Branch to switch from SpiderMonkey to Node.js From: Benoit Chesneau To: "dev@couchdb.apache.org" Content-Type: multipart/alternative; boundary=14dae9340e6ff885b704d49741d3 X-Virus-Checked: Checked by ClamAV on apache.org --14dae9340e6ff885b704d49741d3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Jan 31, 2013 at 4:16 PM, Jason Smith wrote: > > > Yes this is the problem. You are right. This is Jan's answer. CouchDB is > already resilient to a few different runtimes. > > - having more concurrency for couchapps and view indexation > > > > Love it, but out of scope in this thread. > > > > > > 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. > > > > Love it, but of scope in this thread. > 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. > > > > The second, need some discussions. I'm with randall, I think that porti= ng > > couchjs to v8 is not that hard and would really solve the problem. > > > I have working code. The test suite passes. I would love to see working, > passing v8 code so we could compare and contrast. > That should be possible. I need to find some time too. couchbase has already a m/r thing using v8. > > 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. > 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. > > Can someone please specifically describe a "sandbox" feature? CouchJS > passes the test suite. So what does the sandbox do? > did it many time. See my other mail where I tried to summarise it again. - beno=EEt --14dae9340e6ff885b704d49741d3--