That's the goal of the Common Language Interface subproject, yup :) Subgoal one, behind releasing the first mod_aspdotnet module, is to separate the COM instantiation from the rest of the System.Web support. This will allow folk to plug other CLR environments into our framework. Then, begin declaring Apache.Web classes that get right to the heart of the httpd server to write Apache modules in any preferred language.
It sounds like everyone is on the same page. Bill At 01:55 PM 8/9/2004, Jeff White wrote: >If the fully compiled Apache2 Windows >MSI release version included a fully >compiled C++ .NET "assembly loader" >module (even if only in the experimental >folder), then many other developers >would be able to start "a playin' and a >learnin'" the .NET Framework classes >and the .NET Framework's many config >files (for Apache web server usage) by >writing these Apache .NET Framework >assemblies via the free .NET Framework >SDK compilers or with the many other third >party .NET enabled compilers..... > >Most of these assemblies could be written >in the computer language that the user knows >best or the user could learn a "new" language, >if the user wishes to do so..... > >Also these Apache .NET assemblies could >"host" ASP.NET themselves (or not) or could >just be used with the many .NET Framework >classes (to do what ever these Apache users >want or need)..... > >Jeff
