On 8/18/2012 8:39 AM, Jim Jagielski wrote:
On Aug 17, 2012, at 11:01 PM, Jess Holle <je...@ptc.com> wrote:\
"Downstream customers" in my case means customers that will deploy Apache and
our products on their own servers. In a great many cases these servers run Windows.
Ahh. That explains it.
The Windows MPM is designed to be the most optimal implementation
for Windows servers, dedicated and specific to Windows. What is
it about the Windows MPM which is inadequate to your or your
client's needs? We have direct access to Microsoft engineers,
so I think they would also be curious as well. MS is quite
interested in ensuring Apache httpd runs extremely well on
Windows.
The Windows MPM does indeed work rather well.
That said, if one has a lot of long running connections that are mostly
idle won't one run into exactly the same issues that mod_worker has vs.
mod_event? What's the strategy for dealing with large numbers of
long-poll requests, long HTTP keepalive settings, etc, with the Windows MPM?
Similarly what's the strategy for this on UNIX when /all /the requests
in question are HTTPS?
Again, we've not hit the "limit" there with mod_worker, but a major
interest in 2.4.x was raising the "ceiling" in this direction.
--
Jess Holle
