Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Errors-To: <wrowe@rowe-clan.net>
Message-Id: <6.1.2.0.2.20041002001733.0db79c50@pop3.rowe-clan.net>
Date: Sat, 02 Oct 2004 00:35:44 -0500
To: general@incubator.apache.org
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
Subject: Re: Where proposal should be sent?
In-Reply-To: <001401c4a82a$ab68a030$0100000a@keldorfortress>
References: <NBBBJGEAGJAKLIDBKJOPOEHJMHAB.noel@devtech.com>
 <001a01c4a74c$9571c1f0$0100000a@keldorfortress>
 <6.1.2.0.2.20041001134015.0cc9bec0@pop3.rowe-clan.net>
 <001401c4a82a$ab68a030$0100000a@keldorfortress>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

At 09:51 PM 10/1/2004, hammett wrote:
>----- Original Message -----=20
>From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
>
>> 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 :-)

Please do :)  Contrawise, I'll need to start looking at some of the
proposed project components of Castle ;)

>> 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=E7ades for=
 request,
>response, session, application and dispatch the call? Well, better have a
>look at the code.. I know.. ;-)

MS Win32-specific implementation, it uses the COM interface to
instantiate the MS System.Web.Hosting container.  We implement
System.Web.Host / System.Web.Request.  MS ASP.NET does most=20
of the rest, we just do the lifting.

>> 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?

Authoring of in-process modules written in .NET, with all of=20
the support for managed .NET code environment, and hooking back=20
into the native process which the httpd binary is running in.

Obviously, there is alot of thunking involved.

If you are curious about the httpd module API,=20

 =
 http://cvs.apache.org/viewcvs.cgi/httpd-2.0/modules/experimental/mod_exampl=
e.c?rev=3D1.48&view=3Dauto

is long on descriptions, doesn't do much.

http://perl.apache.org is the most complete interface to httpd
(and it's underlying apr portability layer) that allows pretty
much complete access to handling requests within httpd's API.
That's the level of binding that I'm most interested in.

Bill


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org