At 03:09 PM 2/28/2005, Wayne S. Frazee wrote: >William A. Rowe, Jr. writes: >>I'd argue the opposite, we aren't refining 2.x sufficiently for folks to >>garner an advantage over using 1.3. It simply isn't more effective for them >>to use 2.0 (having tried both.) > >Further, I would submit that there has been little movement in part because >man of the hosting infrastructure systems that the average hosting provider >uses are tied to the 1.3 apache version.
Oh, I have no doubt that the only time a large ISP would be interested in 2.0 is when deploying whole new frameworks for incoming users. Few will fight the battle to mass-migrate hundreds of existing vhost users. I don't think we expect the 1.3 to disappear in the next five years, anymore than we saw 1.2 disappear quickly. It does just what it needs to do and won't disappear from many boxes till those boxes bite the dust. >A move to 2.0 or 2.1 will take place gradually over time, I think, once PHP >can be used with some expectation of stability on a non-prefork-MPM. Note: I >am not insinuating PHP is not thread safe, but rather many of the elements it >works with or relies on are not. I also want to make it clear, I am not >blaming the PHP community either. I wasn't originally commenting on the uptake. I was actually commenting on what appears to be a reverse slide from 2.0.5x -> 1.3.33. I'm not even worried if the adoption of Apache 2.0 doubles. I'm more concerned if we aren't satisfing those willing to just try the move to 2.0.5x, who jump back when a new 1.3 is announced. That is worrying to me. Bill
