I've written a nodejs http service that I've configured to run as an xinetd
service (basically the service receives the connected socket as
process.stdin/stdout). When the service runs it creates a http server and
then emits a 'connection' event with process.stdin.
server = http.createServer(connectCB);
server.emit('connection', process.stdin);
Sometimes the connect callback is called sometimes not and what I came to
realize is that when it doesn't run it is because it didn't get the 'data'
listener configured in time and it missed the http request. I also tried
using a nodejs net.Server that forks a child_process and passing the socket
with a send call but it suffers from the same issue. In the net.Server
version I tried doing a socket.pause in it's connect callback and a
socket.resume in the child process but that didn't make it work any more
consistently. I think this is something that more than myself would like to
be able to do. Anyone have thoughts on how to resolve or work around this
issue?
Ted
--
--
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.
