An off-the-shelf node can't execute *JavaScript* code in parallel (*), because
*only* *one* of its *multiple* threads runs a (single) v8 JS VM.
But a node with the threads-a-gogo module can create as many (up to thousands)
additional V8 JS VMs as needed, and execute javascript code truly in para
On Fri, Sep 7, 2012 at 1:16 PM, Jimb Esser wrote:
> It sounds like you might be misunderstanding something fundamental about
> node/Javascript - it's all single threaded, and (at least the networking
> stuff) is event-based (specifically a stream of sequential events, since
> there's no concurren
It sounds like you might be misunderstanding something fundamental about
node/Javascript - it's all single threaded, and (at least the networking
stuff) is event-based (specifically a stream of sequential events, since
there's no concurrency). In your example, while it's running line 5,
there'
On Fri, Sep 7, 2012 at 12:01 PM, mscdex wrote:
> On Sep 7, 10:21 am, Mark Volkmann wrote:
> > On Fri, Sep 7, 2012 at 9:09 AM, Ben Noordhuis
> wrote:
> >
> > The client queues write requests until the connection handshake is
> >
> > > done. Said handshake is complete when the server accepts the
On Sep 7, 10:21 am, Mark Volkmann wrote:
> On Fri, Sep 7, 2012 at 9:09 AM, Ben Noordhuis wrote:
>
> The client queues write requests until the connection handshake is
>
> > done. Said handshake is complete when the server accepts the
> > connection, which node does right before it calls your conn
