I've been working on a web server framework of my own using a cluster of workers sharing a single listener. The documentation for clusters just says that workers workers sharing a listener will just automagically throttle themselves, but I find that unacceptable.
I want to be able to tell a listener in one of the workers to not accept new connections until I unblock it. I have found only one way of doing this and it's much less than satisfactory. You can call the close method on the server which will stop the server from accepting new connections, but the only way to restart it is to create a new server! This works, but a) it's creating a new server instance when all I really want to do is allow new connections to be accepted again, and b) I'm not sure how the backlog works in a node HTTP server. Is there a way to tell how large the backlog is? is there some way to just configure the maximum number of concurrent connections per listener? Is the backlog shared across all of the shared listeners in all of the workers? Is there documentation somewhere on the underlying implementation? -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
