Path: ...!weretis.net!feeder9.news.weretis.net!panix!.POSTED.spitfire.i.gajendra.net!not-for-mail
From: cross@spitfire.i.gajendra.net (Dan Cross)
Newsgroups: comp.os.vms
Subject: Re: Apache + mod_php performance
Date: Wed, 2 Oct 2024 15:07:44 -0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Message-ID: <vdjnk0$2ob$1@reader1.panix.com>
References: <vcv0bl$39mnj$1@dont-email.me> <vdjjpv$37f8q$2@dont-email.me> <vdjme2$r42$4@reader1.panix.com> <vdjmq4$37f8q$3@dont-email.me>
Injection-Date: Wed, 2 Oct 2024 15:07:44 -0000 (UTC)
Injection-Info: reader1.panix.com; posting-host="spitfire.i.gajendra.net:166.84.136.80";
	logging-data="2827"; mail-complaints-to="abuse@panix.com"
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: cross@spitfire.i.gajendra.net (Dan Cross)
Bytes: 1606
Lines: 20

In article <vdjmq4$37f8q$3@dont-email.me>,
Arne Vajhøj  <arne@vajhoej.dk> wrote:
>On 10/2/2024 10:47 AM, Dan Cross wrote:
>>[snip]
>> You do not seem to understand how this is qualitatively
>> different from your test program not sending `Connection: close`
>> with its single request per connection, and then blocking until
>> the server times it out.
>
>It is qualitative different from what you are imaging.
>
>The client does not block until the server times out.

So what, exactly, does it do?  And what is the "problem" that
you are imagining here?  Please be specific.  Better yet, why
don't you post your test program somewhere so folks who
understand how the protocol works can look at it and point out
the bug?

	- Dan C.