Re: [node-dev] built-in objects

2012-07-22 Thread Dominic Tarr
oh, oops, other way around. EventEmitter is the superclass. Stream is the subclass. On Sun, Jul 22, 2012 at 10:48 PM, mscdex wrote: > On Sunday, July 22, 2012 6:07:22 AM UTC-4, Dominic wrote: >> >> EventEmitter for example, is core element because it's the subclass of >> Stream which is the subc

Re: [node-dev] built-in objects

2012-07-22 Thread mscdex
On Sunday, July 22, 2012 6:07:22 AM UTC-4, Dominic wrote: > > EventEmitter for example, is core element because it's the subclass of > Stream which is the subclass of every IO stream. (it's not a utility > for interoperability) Huh? EventEmitter isn't a subclass of Stream.

Re: [node-dev] built-in objects

2012-07-22 Thread Dominic Tarr
one way of putting it is to say that node core needs just enough functionality to build a package manager. EventEmitter for example, is core element because it's the subclass of Stream which is the subclass of every IO stream. (it's not a utility for interoperability) Strictly speaking, http is a

[node-dev] built-in objects

2012-07-22 Thread beachdog
I'm coming up to speed on the node core, trying to learn things at a very detailed level because I need something for my application area that will probably be a lot like node -- either using node itself or developing a similar v8-based framework for my purposes. And I am interested in the dec