Symbulos Partners wrote:
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.
php5 + Apache 1.3.33 works just fine, have you tried that? I would DEFINITELY wait until PHP 5.1 to put it into production though, there are a number of features being added, as well as the time spent testing and developing php 5 will help assure its stability as well. If you have the possibility of setting up a test server on another port to test php5 with apache 1.3.33, this will be your safest bet to develop the software you will use without compromising the current setup.
You might also experiment with setting up Apache2 on another port, and then once you can be sure that your solution works in Apache and in Apache2, you have the ability to switch back to Apache in the blink of an eye just by modifying which port each process is listening to. It would require maintaining parallel setups for a while, which is a real pain, but you would get the cutting-edge features you are looking for with a safety fallback, which your clients would be looking for.
Greg
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
