incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "hammett" <>
Subject Re: Where proposal should be sent?
Date Sat, 02 Oct 2004 02:51:08 GMT
----- Original Message ----- 
From: "William A. Rowe, Jr." <>

> I'm curious about the interoperability this could provide us, as
> we hope to extend to MS NET, mono, etc, an httpd module API.

While I think the same time this could be done, we have some divergence of
focus. Or maybe I'm wrong.
In my understanding your mod_aspdotnet needs to be really really fast, for
obvious reasons. The same is not true for castle where we'd like to have
correctess and good contracts before focus on performance.

But I'd like to browse the mod_aspdotnet code. I don't understand much of
Httpd, but I happen to be an author of an ASP.Net book :-)

> This phase is nearly finished, a few bugs were pointed out and
> another build variant, based on the free Visual C++ NET compiler,

So how's the strategy? Your mod, C or C++ based instantiates the .Net COM
component to have an managed environment, build proper fa├žades for request,
response, session, application and dispatch the call? Well, better have a
look at the code.. I know.. ;-)

> is due before a general release of the MS-specific mod_aspdotnet.
> Once done, other than bug fixes and users, I don't see much
> excitement there.  The next action item is to start looking
> at exposing the native httpd environment to an arbitrary .NET
> hosted httpd module.

What do you mean by native httpd environment?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message