Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion about porting node.js on Android

Received: by 10.180.104.133 with SMTP id ge5mr167971wib.1.1340294826697;
        Thu, 21 Jun 2012 09:07:06 -0700 (PDT)
X-BeenThere: nodejs-dev@googlegroups.com
Received: by 10.180.90.19 with SMTP id bs19ls8619707wib.4.canary; Thu, 21 Jun
 2012 09:07:02 -0700 (PDT)
Received: by 10.180.98.199 with SMTP id ek7mr1643533wib.0.1340294822153;
        Thu, 21 Jun 2012 09:07:02 -0700 (PDT)
Received: by 10.180.98.199 with SMTP id ek7mr1643532wib.0.1340294822141;
        Thu, 21 Jun 2012 09:07:02 -0700 (PDT)
Return-Path: <hel...@gmail.com>
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179])
        by gmr-mx.google.com with ESMTPS id e10si8796446wiz.3.2012.06.21.09.07.02
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 21 Jun 2012 09:07:02 -0700 (PDT)
Received-SPF: pass (google.com: domain of hel...@gmail.com designates 209.85.212.179 as permitted sender) client-ip=209.85.212.179;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of hel...@gmail.com designates 209.85.212.179 as permitted sender) smtp.mail=hel...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-wi0-f179.google.com with SMTP id hr4so471349wib.14
        for <nodejs-dev@googlegroups.com>; Thu, 21 Jun 2012 09:07:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=b/SpShxOJkNB98163ggJxDr5LYxXYXtRCmlxbvddJjE=;
        b=b0N5/kIygSK4RFuGGv+8LFFfSmtII5Syq8E/u/p6gJHCPVzxgk/96QX+krkpPP2Zp5
         /cN1A+K4Nwh9ZlCkHumSiSP4Tl8pZLLbUmDy3pVtRoegqucPj8HB7pgSa7ZJjsRNL90k
         ZsK1Tmn5LivNE0AvqWEZR2opisbbwrsk7mm9LELK5+70pDlQ1FGKjarGZHAIZgf93sGa
         skP8LmQQ2KiOuQnrfGHOfGqzxmb5DXrKLuB8Nbvn+SZd0GOnqZVOF5Cj03OoENRxrCOr
         sVAJTOUj3RTh84F9VA4+2Bxn9drNuoSa9ZiEPtpwum9OAUHu/tgXvGlDLtPZyKa8BJWn
         LbEA==
MIME-Version: 1.0
Received: by 10.217.1.202 with SMTP id n52mr2206913wes.21.1340294821948; Thu,
 21 Jun 2012 09:07:01 -0700 (PDT)
Received: by 10.223.70.201 with HTTP; Thu, 21 Jun 2012 09:07:01 -0700 (PDT)
In-Reply-To: <CAJkwh4J2XN+yhUeup0GRVcHq7Ny+ddHvkKo3DJ0WAb32e7g...@mail.gmail.com>
References: <CAEXHaurbTw5kJZ0bDQ+BEOwti=anisbn7MCRmi0XUPLiLUZ...@mail.gmail.com>
	<CABEaZaskb3r8uSGOXx6PCn-CZv8r2nZEgiku=nC2+UO3YYu...@mail.gmail.com>
	<CAJkwh4J2XN+yhUeup0GRVcHq7Ny+ddHvkKo3DJ0WAb32e7g...@mail.gmail.com>
Date: Thu, 21 Jun 2012 12:07:01 -0400
Message-ID: <CAPJ5V2YgmubPsd_O677PB_Y-K91kwSj-S0MSEAC3Qwi2LpA...@mail.gmail.com>
Subject: Re: [node-dev] about porting node.js on Android
From: Matt <hel...@gmail.com>
To: nodejs-dev@googlegroups.com
Content-Type: multipart/alternative; boundary=20cf301e2e7dc1ac2d04c2fdb438

--20cf301e2e7dc1ac2d04c2fdb438
Content-Type: text/plain; charset=UTF-8

On Thu, Jun 21, 2012 at 11:42 AM, Gustavo Machado <machad...@gmail.com>wrote:

> I'm intrigued, what would be the most common use cases for using node.js
> in the phone?


Making Android web scale.

--20cf301e2e7dc1ac2d04c2fdb438
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 21, 2012 at 11:42 AM, Gustavo Machado <span dir=3D"ltr">&lt;<a =
href=3D"mailto:machad...@gmail.com" target=3D"_blank">machad...@gmail.com</=
a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
I&#39;m intrigued, what would be the most common use cases for using node.j=
s in the phone?</blockquote><div><br></div><div>Making Android web scale.</=
div></div>

--20cf301e2e7dc1ac2d04c2fdb438--