Date: Sun, 8 Apr 2012 10:59:20 -0700 (PDT)
From: Pedro Teixeira <pedro.teixe...@gmail.com>
To: nodejs@googlegroups.com
Cc: oliver.le...@gmail.com
Message-ID: <6781023.867.1333907960592.JavaMail.geo-discussion-forums@vbyj26>
In-Reply-To: <CAOYEtUXPi8tghBvZmLEWuGjY3X=w17S_nbNTDQi1m-p7Ley5Ew@mail.gmail.com>
References: <23296910.487.1333875844462.JavaMail.geo-discussion-forums@vbyj26>
 <CAOYEtUWqMZD1cBx=d3ZSGTcXe9GH9EQO+uhc-o8rymg=e+xNow@mail.gmail.com>
 <267321667002496447@unknownmsgid>
 <CAOYEtUXPi8tghBvZmLEWuGjY3X=w17S_nbNTDQi1m-p7Ley5Ew@mail.gmail.com>
Subject: Re: [nodejs] delegating event emitter
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_865_10224936.1333907960591"

------=_Part_865_10224936.1333907960591
Content-Type: multipart/alternative; 
	boundary="----=_Part_866_18259987.1333907960591"

------=_Part_866_18259987.1333907960591
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Thanks, I know that.

My question still remains:

Are there any plans to support this on Node Core in order to make it 
standard or does any one has anything to say agains this piece of 
functionality?

On Sunday, April 8, 2012 6:29:07 PM UTC+1, Oliver Leics wrote:
>
> On Sun, Apr 8, 2012 at 5:25 PM, Pedro Teixeira <pedro.teixe...@gmail.com> 
> wrote:
> > Yes, thanks, I know that's an option.
> > Are there any plans to standardize this into core?
>
> Question is, why?
>
> The core EventEmitter-class is pure javascript, nothing fancy, just
> the very basics. It is sufficient for almost all situations. The more
> you add to this basics, the more overhead/inefficiency you'll get in
> return.
>
> If it is really not sufficient, a simple 'npm install eventemitter2'
> or dependency to eventemitter2 in package.json , then
> require('eventemitter2') - and hooray, and you can use it.
>
> But if I would need only what you described, I would overwrite 'emit'
> of the EventEmitter. Its not that hard, EventEmitter of nodes
> events.js is pure JS.
>
>
------=_Part_866_18259987.1333907960591
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Thanks, I know that.<div><br></div><div>My question still remains:</div><di=
v><br></div><div>Are there any plans to support this on Node Core in order =
to make it standard or does any one has anything to say agains this piece o=
f functionality?</div><div><br>On Sunday, April 8, 2012 6:29:07 PM UTC+1, O=
liver Leics wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0;marg=
in-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">On Sun, Apr =
8, 2012 at 5:25 PM, Pedro Teixeira &lt;<a href=3D"mailto:pedro.teixeira@gma=
il.com" target=3D"_blank">pedro.teixe...@gmail.com</a>&gt; wrote:<br>&gt; Y=
es, thanks, I know that's an option.<br>&gt; Are there any plans to standar=
dize this into core?<p>Question is, why?</p><p>The core EventEmitter-class =
is pure javascript, nothing fancy, just<br>the very basics. It is sufficien=
t for almost all situations. The more<br>you add to this basics, the more o=
verhead/inefficiency you'll get in<br>return.</p><p>If it is really not suf=
ficient, a simple 'npm install eventemitter2'<br>or dependency to eventemit=
ter2 in package.json , then<br>require('eventemitter2') - and hooray, and y=
ou can use it.</p><p>But if I would need only what you described, I would o=
verwrite 'emit'<br>of the EventEmitter. Its not that hard, EventEmitter of =
nodes<br>events.js is pure JS.<br></p><p></p><p></p><p></p></blockquote></d=
iv>
------=_Part_866_18259987.1333907960591--

------=_Part_865_10224936.1333907960591--