From: "William A. Rowe, Jr." Before starting remember one says apples the other says pears but it's all fruit! :)
> That's the goal of the Common Language > Interface By the way, does the CLI include: System.Web System.Data System.WinForms (and any (?) .NET 2.0 goodies) > subproject, yup :) Subproject? Why not first with a simple "hello world" Apache2 .NET module by using (MC++) Managed Extensions? More on this latter... > Subgoal one, behind releasing the > first mod_aspdotnet module, So nothing will (can) be done until "mod_aspdotnet" is first released? Which is when? And the reasons why mod_aspdotnet must be first? > Subgoal one, behind releasing the first > mod_aspdotnet module, is to separate > the COM instantiation from the rest of the > System.Web support. I do not follow, please explain..... > This will allow folk to plug other CLR > environments into our framework. I am lost again, "other CLR environments"? "into our framework"? Please provide a simple worded example of these.... > Then, begin declaring Apache.Web > classes that get right to the heart of > the httpd server to write Apache modules > in any preferred language. Please provide a simple worded example of these "right to the heart".... Also will there not be Apache.Admin "type" classes or even Apache.Dev "type" classes or Apache.Basic.Mod "type" classes? Allowing "any type" of assemblies to be loaded will increase the above classes chances of development.... (free SDK compilers) By releasing a simple .NET assembly loader, this would allow the learning of the .NET classes, as well as learning "hosting".... No need to have all, get out a .NET C++ that does full COM first, but perhaps that and MC++..... Try a simple MC++ "Hello World" module. For example: Try adjusting the Ryan Bloom's "Example Module", a text Hello World module, on pages 169-174 in his book, Apache Server 2.0. But adjust the text output for "Hello World" into a complete HTML file by using .NET's StringBuilder (to write the html code). Then compile the module as a MC++ file.... Move the module to the test sever, adjust the server's conf file and run the browser. What happens? After this perhaps release a simple assembly loader and away the users will go..... > It sounds like everyone is on the same page. Everyone ;) I've only seen you here! :) Jeff
