Trent Nelson wrote:
From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]
Perhaps you are thinking of the idea of an mpm_winhttp,
using the WinHTTP API (which handles the request/response
in the WinXP HTTP stack and then dispatches between multiple
hosts and uri's that are registered with this API)?
Interesting idea; how serious were you being? ;-) What you're
suggesting sounds like a complete inversion of how something like
mod_aspdotnet works. That is apache httpd becomes the
``System.Web.Hosting''-esque container and WinHTTP facilitates all the
request/response handling.
I have no plans at present to actually do this but the idea's been brought
up by a couple people here. Yes, the mpm would replace the core HTTP
protocol filters (WinHTTP would pass incoming headers in an array, and then
return outgoing headers in an array), it would replace the core network
filters with a pull/push to WinHTTP api, it should probably keep a table
of the WinHTTP connectors associated with the VHosts so it's trivial to
dispatch them. Otherwise it would appear as a normal Apache request to
the rest of the modules. Oh - this wouldn't be .NET at all.
What sort of benefits do you see that having?
Mostly for servers which -must- serve IIS requests, application X requests,
and Apache HTTP requests using the same ports, different vhosts.
In other words, not something very interesting to the average httpd dev
participant.
Bill
