Cool, sounds simple. How do you do that when using PoCo::Server::HTTP? Closing a response is mentioned in the context of streaming on the perldoc page.
Since most people use the cookbook, I imagine, when they first start writing POE based programs, should how to close the connection when finished be added? -----Original Message----- From: Andy Grundman [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 21, 2007 1:08 PM To: [email protected] Subject: Re: POE::Component::Server::HTTP, Keep alive, and leaking sockets On Mar 21, 2007, at 1:00 PM, Eric Busto wrote: > In this situation, it isn't entirely clear what layer should take > responsibility for closing sockets when they are no longer needed. > > PoCo::Server::HTTP doesn't necessarily know if the browser is going to > make another request over the same socket. By default, in accordance > with HTTP 1.1 (I believe), the socket is just left open. The socket should be closed by the server after a certain timeout period, for example Apache uses 15 seconds as the default time out for keep-alive connections (KeepAliveTimeout). ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------
