Greetings.
[...]
>
> do you have a simple test case to reproduce the problem?
>
No, I do not. I hope I will be able get/build/test the latest CVS this week,
and perhaps I'll be able to work on making the problem
reproducible/debuggable which may well mean
I'll have to build a debugperl.
Some facts of the threads allocation are making me curious though
(euphemistic to say I don't really understand them). I am running a test
with a counter:
[...]
foreach my $count (0..20) {
$r->puts("<li><b>$count</b></li>\n");
sleep(1);
}
[...]
which I alias to two handlers (say /count1/ and /count2/).
If I then call it from the same browser in three separate frames like this:
| Frame 1 | Frame 2 | Frame 3
| htpp://localhost/count1/ | htpp://localhost/count2/ |
htpp://localhost/count1/
The execution order turns out to be: 1+2 and *then* 3. It looks like a
thread is allocated to this (client,handler) pair, so Frame 1 and 3 are
running in the same thread, separate from the thread that's running 2.
Is this reading correct, and is this behavior amenable to configuration?
(And is this a modperl question or an Apache question?)
> > iib) I then set out to build a debug version. That ain't
> easy.... I finally
>
> this has been fixed in cvs, MP_DEBUG=1 should do the right things now.
>
Great - I'll try it soon.
Cheers,
alf
