Hi, another reason may be mod_perl, althought mod_perl 2.0 is available for quite some time, and there is a good documentation how to migrate applications, many applications based on mod_perl haven't done so. The problem is not the same as for mod_php. mod_php 4.* has been available for apache 1.3 and apache 2 but mod_perl 1 only for apache 1 and mod_perl 2 only for apache 2. Mason(a mod_perl app) for eg. has mod_perl 2 support since 2004-10-18: -snip- As of Mason 1.27 (released 10/28/2004), there is support for Apache/mod_perl 2.0 in the core Mason code -snap-
I have been using 2.0 since 2.0.35 but have damned our decision when serious breakage occured in mod_ssl in combination with various browsers and 3rd party ssl clients between version 2.0.46 and 2.0.49. 1.3, since I use it, never had those problems. Don't take me wrong, I like 2.0 and love it's features and the stability now is far better than when it was introduced, but I can understand people that call it too risky to migrate to 2.0. regards klaus
