Re: migrating to PHP 5 + Apache 2 from PHP 4.3.8 + Apache 1.3.33.

Rasmus Lerdorf wrote: > > As far as threading goes, it is simply not a good idea for a large > complex system. I do not understand why, probably because I am not well prepared. Can you explain me? As far as I know, threading should be a noticeable improvement in case of large systems. Is there something in the implementation of PHP 5 which does not allow for safe threading? If so, what it is? > > I am a big believer in keeping the base infrastructure as simple as > possible. You are going to layer a lot of complexity on top of Apache > and PHP in the form of your web applications. You want to make sure > that your building blocks are rock solid so if you see a problem you can > be confident that it is something you did wrong. If your base is shaky > everything you build on top of it is going to be that much more unstable. I totally agree. Our problem is that we want to use the new php 5 object model, and at the same time would like to move to Apache 2 for several different reasons. There are 4 alternative solutions 0)php 5 + Apache 2 1)php 5 + Apache 2 pre-fork (not totally satisfactory, but better than have a system that is unstable) 2)php 5 + Apache 1.3.33 (which is not totally satisfactory, less than 0,1 in any case, but better than have a system that is unstable) 3)php 4 + Apache 2 (which is not totally satisfactory, less than 0,1,2 in any case, better than have a system that is unstable) which one does satisfy your condition of rock solid foundation? Or shall we stick with php 4 + Apache 1.3.33, which is VERY unsatisfactory because we cannot use the new object model? The server is a production server, so we must have rock solid solutions on it. Thanks in advance. -- symbulos partners -.- symbulos - ethical services for your organisation http://www.symbulos.com