Fwd: ASP.NET support for httpd project?

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

>I'm sending this out as a feeler to discover how large a community one of two
>proposals might have for incubation, and eventual incorporation as subprojects
>of the httpd top-level project.
>
>First proposal, I'm in the process of ensuring that all of the I's are dotted and
>T's are crossed to offer the mod_asp.net module developed by Covalent to
>the ASF.  Important details;  this runs in-process within httpd/win32 only,
>and invokes the Microsoft.NET implementation of System.Web.Hosting
>to support the ASP.NET framework.
>
>Additional proposal, I'd like to investigate extending an invitation to the crew
>of mod_mono, if they would have it, to make such an Apache mod_net 
>implementation pluggable with different front and back ends, much like the
>Tomcat connector project.  In fact, rather than the ASP_NET plugin, one
>alternative will be to use the Tomcat connector, itself, rather than inventing
>the wheel.  I'm led to believe that it's what mod_mono already does.  I should
>really point out that the System.Web classes would not be part of such
>a project, those belong in the .NET implementation - we would be using
>the implementation's System.Web.Hosting classes and exposing our own
>Apache.Web classes to participate as hosts.  Another server front-end 
>plugin could allow Mono to run in-process,  much as the Covalent 
>implementation already does on Win32.
>
>The back-end plugin would extend whatever support is necessary for either
>Microsoft.NET, Mono, or whichever .NET framework would host the module.
>Note that front-ends run as platform native code, while back-ends run within
>the .NET CLR runtime.
>
>What would be *most* cool, and was the original plan (never realized) for
>mod_mono, would be true httpd module creation al la mod_perl.  This would
>certainly have to be the in-process flavor, not the out of process extension
>such as a Tomcat connector.  Perhaps different front-end stubs would allow
>us a single back-end .NET framework design for any .NET implementation.
>But I would expect this to grow out of the experience of building in-process
>connectors from Apache into those .NET frameworks for basic ASP.NET
>services.
>
>So just a straw poll, who would be actively interested in participating in an
>ASF-hosted ASP.NET implementation, first for win32, and secondly for all
>platforms e.g. mod_mono revisited, as an ASF entity?  If you are answering
>*hell ya* - I expect to add your name to the proposal for incubation, so be
>careful what you ask for :)
>
>I should have code to present to the ASF with the contribution form all
>set up, I'd formally propose this for incubation, once all of that is in place 
>and I have a list of the group of us interested in evaluating this and behind 
>the first community.  Consider this the proposal-before-the-proposal.
>
>Note I originally posted this to PMC - but thought that there may be several
>non-httpd contributors who might be interested in some of this proposal.
>
>Bill



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