>> >
> > Perhap Apache on Windows needs updating?
>
> Perhap Apache on Windows needs to have patches offered. HTTP.SYS
> is an interesting technology and certainly fits the profile for
> an entirely separate MPM and core network stack, unrelated to the
> conventional httpd server. Several folks have kicked around the
> idea, but this is OPEN SOURCE SOFTWARE. Until someone feels like
> doing to the work, it won't exist, and trolling doesn't encourage
> solutions in open source.
>
It had nothing to do with trolling - but explaining more than one process
on a port at the same time information - Apache can use it too!
> On that friendly note;
As for patches - it's more than that - it is a completely new project!
And it is easy to start learning http.sys via PowerShell - even tracking
Apache via PowerShel (threads, sockets, processes and etc.). Then after
seeing "non Unix" ways, not non HTTP ways, and how they work, well if
one wants to move on to C++ / C okay but .NET makes it so much easier
for the starter now! PowerShell is a .NET processe that can use http.sys.
So one can start right at the command line and see usage and objects
and properties and etc right now (of Apache and or of http.sys). But all
this is not Apache On Windows Unix version software - just newer Windows
actions doing standard HTTP actions like IIS or any other http.sys user!
But the real question for ASF is - why write something that is already
there - one can change any part of IIS 7 (and up). So why not just
start ASF IIS modules or what ever? Still open source and usable.
Then perhaps move on to (if needed) to Apache http.sys MPM!
Just a question!
_________________________________________________________________
Windows Live™ Contacts: Organize your contact list.
http://windowslive.com/connect/post/marcusatmicrosoft.spaces.live.com-Blog-cns!503D1D86EBB2B53C!2285.entry?ocid=TXT_TAGLM_WL_UGC_Contacts_032009
