On 24/03/07, David Davis [EMAIL PROTECTED] wrote:
I used 'sudo ngrep port 32080' and watched ls /proc/pid/fd/ while I hit
the http server.
I noticed that the responses were HTTP/1.0 but I didn't see a connection:
close header.
So, I set $response-protocol( HTTP/1.1 ); in the cookbook example,
.
-Original Message-
From: Maciej Pijanka [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 27, 2007 1:51 AM
To: POE List
Subject: Re: POE::Component::Server::HTTP, Keep alive, and leaking
sockets
On 24/03/07, David Davis [EMAIL PROTECTED] wrote:
I used 'sudo ngrep port 32080' and watched ls /proc
PM
To: Eric Busto
Cc: poe@perl.org
Subject: Re: POE::Component::Server::HTTP, Keep alive, and
leaking sockets
My memory is fuzzy, but I think if you close the browser,
especially if it's local, the sockets closes. I remember IE keeping
the
connections alive
, 2007 12:27 PM
To: Eric Busto
Cc: poe@perl.org
Subject: Re: POE::Component::Server::HTTP, Keep alive, and
leaking sockets
My memory is fuzzy, but I think if you close the browser,
especially if it's local, the sockets closes. I remember IE keeping
From what I have gathered, for a web server to be HTTP 1.1 compliant, it
must support keep alive, and keep alive is enabled by default.
When using POE::Component::Server::HTTP in its simple case, as in the
cookbook entry
http://poe.perl.org/?POE_Cookbook/Web_Server_With_Components, keeping
the
My memory is fuzzy, but I think if you close the browser, especially if it's
local, the sockets closes. I remember IE keeping the connections alive for a
while.
On 3/21/07, Eric Busto [EMAIL PROTECTED] wrote:
From what I have gathered, for a web server to be HTTP 1.1 compliant, it
must support
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mathieu Longtin
Sent: Wednesday, March 21, 2007 12:27 PM
To: Eric Busto
Cc: poe@perl.org
Subject: Re: POE::Component::Server::HTTP, Keep alive, and
leaking sockets
My memory is fuzzy, but I
::Component::Server::HTTP, Keep alive, and
leaking sockets
My memory is fuzzy, but I think if you close the browser,
especially if it's local, the sockets closes. I remember IE keeping the
connections alive for a while.
On 3/21/07, Eric Busto [EMAIL PROTECTED] wrote
@perl.org
Subject: Re: POE::Component::Server::HTTP, Keep alive, and
leaking sockets
My memory is fuzzy, but I think if you close the browser,
especially if it's local, the sockets closes. I remember IE keeping
the
connections alive for a while.
On 3/21/07, Eric Busto
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.
finished be added?
-Original Message-
From: Andy Grundman [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 21, 2007 1:08 PM
To: poe@perl.org
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
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
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
-
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
14 matches
Mail list logo
