Keep-Alive, Apache processes and $r->connection

Hi.

Am I right, or horribly wrong, to assume that in case of a "keep-alive"
client connection, the multiple requests sent over that connection will
be processed by the same Apache "process" (child or thread) ?

I am assuming the above, from the fact that there exists a
$request->connection->notes table. It seems that it would make little
sense for such a structure to exist otherwise.

Thanks
André

Re: Keep-Alive, Apache processes and $r->connection

André Warnier wrote:
> Hi.
>
> Am I right, or horribly wrong, to assume that in case of a "keep-alive"
> client connection, the multiple requests sent over that connection will
> be processed by the same Apache "process" (child or thread) ?
>
> I am assuming the above, from the fact that there exists a
> $request->connection->notes table. It seems that it would make little
> sense for such a structure to exist otherwise.

That is correct, You can also write other protocol handlers to run
under apache that are long running conversations like SMTP (ie:
Apache::Qsmtpd), or do the same using the C module api (ie: mod_smtpd),
so it's not necessarily just about keep-alive in HTTP.

Adam

Re: Keep-Alive, Apache processes and $r->connection

On Sun 21 Dec 2008, André Warnier wrote:
> Am I right, or horribly wrong, to assume that in case of a
> "keep-alive" client connection, the multiple requests sent over that
> connection will be processed by the same Apache "process" (child or
> thread) ?
>
> I am assuming the above, from the fact that there exists a
> $request->connection->notes table.  It seems that it would make
> little sense for such a structure to exist otherwise.

Yes, and there is also a $r->connection->pnotes hash to store perl data=20
structures.

Torsten

=2D-=20
Need professional mod_perl support?
Just hire me: torsten.foertsch@gmx.net