We could bring it in with very little to no modifications. Worst case I already made the prototype one instanced :) Sent on the TELUS Mobility network with BlackBerry
-----Original Message----- From: Ken Wallis <[email protected]> Date: Tue, 6 Dec 2011 18:17:27 To: [email protected]<[email protected]> Reply-To: [email protected] Subject: Re: [DISCUSS] Switching out Channel's in callback-js for an event module Haven't checked it out at all, but does it have any additional baggage? I guess the comment that we would need to stub out some stuff makes me think that it might? ----- Original Message ----- From: Patrick Mueller [mailto:[email protected]] Sent: Tuesday, December 06, 2011 05:50 PM To: [email protected] <[email protected]> Subject: Re: [DISCUSS] Switching out Channel's in callback-js for an event module On Tue, Dec 6, 2011 at 17:11, Gord Tanner <[email protected]> wrote: > Key point is I like the eventEmitter idea better. So, a basic question that springs to mind is: can we just use Node's EventEmitter? IIRC, I actually managed to get Node's EventEmitter class to run successfully in the browser; no code changes required, I don't think. But likely stubbing out some module pre-reqs from Node. Work was done here, I can resurrect it if we want to look into it. https://github.com/pmuellr/lumpgap -- Patrick Mueller http://muellerware.org --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
