I've gotten 2 very good reviews of this driver so far. Both have a decent amount of traffic with one getting up to 300,000 hits per hour (if I am reading the stats correctly). They had major thrashing and other issues with the standard httpd driver. The only problem is with the rewrite rules in .htaccess. I can't get them to work for the friendly urls on Joomla. So maybe if I can get a few more testers, someone can figure that part out. I'll post a few things that I tried but didn't work some other time.

No it doesn't. I wouldn't switch it any time soon either. Too many variances makes debugging much harder. I like to change one thing at a time. I ask for testers and have had maybe 3 so far. Can you imagine how bad it would be if I used a httpd 2.4.2 and have just 3 people test and then it goes into a release and is found to be incomplete?

They work just not as default. It is something I am still working on.

In my experience (especially when working for my fork), solution for speed-up httpd (in case Wordpress multisite):

1. using php-fpm + fastcgi --> because less memory usage compare to mod_php and suphp; speed like 'standard' mod_php with security like mod_php_ruid2
2. using php 5.3.x version --> php 5.3.x faster than 5.2.x

Also this driver has disk caching enabled for php files that allow them to be cached. Unlike other webservers, this caching follows the documented standards of what should be cached and doesn't just cache everything like Varnish or nginx does.

That content should have never been cached to begin with. httpd does not cache php files with POST or cookies. nginx and varnish do, which I don't like.

  # Default request checks

        if (req.request != "GET" &&
        req.request != "HEAD" &&
        req.request != "PUT" &&
        req.request != "POST" &&
        req.request != "TRACE" &&
        req.request != "OPTIONS" &&
        req.request != "DELETE") {
        # Non-RFC2616 or CONNECT which is weird.
        return (pipe);
        }

        if (req.request != "GET" && req.request != "HEAD") {
        # We only deal with GET and HEAD by default
        return (pass);
        }

        ## Modified from default to allow caching if cookies are set, but not http auth
        if (req.http.Authorization) {
        /* Not cacheable by default */
        return (pass);
        }