> From the list, the APR API is done. So there should be no further issues
> getting it to work.(As in, you should no longer have to jump through
> hoops every month or release, just to keep up with apr).
Well, this is simply not true. Things are still changing.
-Rasmus
--
PHP General Mailin
I'm trying to exercise PHP on Apache2 for benchmarking of the different
MPMs (worker v. prefork) v. Apache 1.3. Actually *running* apache2 in
prod is not my goal. This is for testing and potentially finding
problems with either PHP, or Apache2, or both(in this case).
>From the list, the APR API
It won't work simply because Apache 2.0 is very much in a state of flux.
The API's change constantly. We are many months away from any sort of
stable Apache2+PHP system. Unless you are a developer and can help fix
problems, you are much better off sticking with Apache 1.3.x and not
bugging the d
The PHP-Dev list doesn't want to hear it, so I guess I'm *stuck* back
here.
Will someone please tell me why the latest CVS of PHP won't let Apache
2.0.32 work and when a graceful fix will be implemented?
Hmm..this sounds like it should go to the dev list...
--
Austin Gonyou
Systems Architect,
4 matches
Mail list logo
