All of your suggestions are very good, the problem is that all of these solutions will introduce too much overhead. I know that a lot of the overhead is very, very minimal, but we cannot afford ANY overhead at all.
Thanks, Nick Cipollina -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Bennett Sent: Thursday, August 02, 2007 6:38 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Socket API problem Hi Nick, I don't have an answer to your licensing problem, but have you considered running your listener from inetd or a similar superserver? In this setup your inetd daemon (or service on windows) listens on your known port, when a request comes in the superserver starts a UV process to handle the incoming request (received on stdin so get the data with INPUT or GETS) send your response using print. This is slightly slower per request than prestarting all your phantoms but you only use as many licences as your peak load and if you have one of the more advanced inetd versions you can limit the maximum number of simultaneous requests (other requests will be queued by inetd). I have implemented a HTTP server using this setup and other than the uv licensing cost it works well. regards, Craig ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
