Hello, First of all I am having a bit of an issue. I have been a PHP 
developer for many years now. I have always seen a need for sockets in JS. 
Recently I am trying to come up with a nodejs for the company I am 
currently working for. What I am looking for is a way to have a single app 
that listens for io.on events then dispatches them to a different app. Thus 
freeing up the primary app to accept more requests and allow the second app 
to do the heavy lifting then pass the socket/event back to the primary app 
when it is done. My boss found something like this in spidermonkey but I 
have yet to figure out how to achieve this with Node. The second point I am 
trying to achieve is having a main apps that get compiled when the are 
created. Currently my boss it not happy with the idea of having to restart 
the node app each time we would like to change or add to it. Currently I 
have written a node app to serve out json object files through a socket io 
connection but, it is in a single app. We are looking for something where 
the main app calls the  json app which goes and gets the json sends it to 
the client then checks in with the server when its done. Does anyone know 
how or IF i can achieve something like this. The closest I have gotten was 
using FS to get the second node apps code then eval it. 

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to