Right, which was more or less my point. :) Currently, however, you -do- have to think about it. I'm not suggesting the behavior of PoCo::HTTP::Server be changed to have keep alive disabled by default, but with the way things are now, a long running application that uses PoCo::HTTP::Server and receives actual HTTP requests will leak sockets, if the code is taken straight from the cookbook example.
-----Original Message----- From: Andy Grundman [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 21, 2007 1:29 PM To: poe@perl.org Subject: Re: POE::Component::Server::HTTP, Keep alive, and leaking sockets On Mar 21, 2007, at 1:12 PM, Eric Busto wrote: > 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? I haven't use Server::HTTP myself, but this sort of thing should probably be handled automatically by Server::HTTP. You really shouldn't have to think about it when writing your own server. ----------------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------------
