Re: Rif: Re: [Phplib-users] is phplib compatible with Apache 2.0?
Brought to you by:
nhruby,
richardarcher
From: Nathaniel P. <np...@te...> - 2005-06-27 14:12:20
|
Fabrizio Ermini wrote: >>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 :-) > > Heh, thanks. ;) >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 > > As long as you're using PHP in a 'prefork' MPM environment (as the post you quoted suggests) then you shouldn't have any real problems. I've been running PHP on Apache 2 for quite a while and it hasn't given me problems, though I admit, I've always used Session4 for sessions of late, so I haven't tested Session '3' on apache 2. >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. > > My understanding of the issue is that thread safety is only a concern with PHP's modules, not any code that may be written in PHP. >>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? > > Well, as you mentioned, your problem is strange enough that I don't have any good idea what would be causing it. Are you using the PHP3-compatible session class for PHPlib pretty much as-is, or have you modified it somehow? If you're using the User class, same question. The problem you describe would have to be in one of those two areas--you might want to make sure that your class isn't getting confused with user data and session data, since they're both stored in the same table by default. Upgrading to session4 may help you--and it may not. But it's something to try. If you can send more details about what exactly is going on (maybe you can add some debugging code to your scripts that prints messages to a log or something), then I might be able to give a better answer. Good luck! -- ___________________________ Nathaniel Price |