On Mon 22 Dec 2008, André Warnier wrote:
> I could do this the hard way by using LWP to just issue a new HTTP
> request to localhost and get the content, before I go on with my
> current request.
>
> But I figure there must be an easier and more efficient way, no ?
>
> Looking at the explanations f
Hi.
I'm in the middle of a PerlHandler. To serve the current request
properly, I would need the result (content) from another HTTP request
which I would maself address to this same webserver.
I could do this the hard way by using LWP to just issue a new HTTP
request to localhost and get the
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 t
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
$r
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->no
Hi.
It is better if you send your messages to the list, not to me
personally. You will get more answers if I am on holiday for example..
Anyway, this line :
LoadFile "/Path/to/your/Perl/bin/perl5x.dll"
is not meant to be taken literally.
It means : replace "/Path/to/your/Perl/bin/perl5x.dll
