> Although I have no idea what's causing the problem (and Apache versions
> /shouldn't/ have anything to do with it)

First of all, glad to read you again, Nathaniel. It's been years since the
last time :-)
What was making me think was the old argument stating that using PHP4 with
Apache 2.0 was a bad idea.
There has been for a long time (I don't know if it's still there) an
"official" statement on PHP site that warned aginst using php 4 on Apache 2
in a production environment.
I can also submit this link reporting a comment by Rasmus about this:
http://apache.slashdot.org/comments.pl?sid=101407&cid=8644732

The problem I'm experimenting it's very random and difficult to diagnose,
so I was starting to think it could be caused by some part of code that's
not thread safe.

> I'd recommend upgrading to
> session4, myself. Provided you didn't alter the existing session API, it
> should be a drop-in replacement.

Yep, but would it correct the problem?

Bye,
Fabrizio





-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Phplib-users mailing list
Phplib-users@[...].net
https://lists.sourceforge.net/lists/listinfo/phplib-users