I had prepared a review of the mod_aspdotnet source code, but was afraid all would call it negative comments. :)
I was told before this is mod_aspdotnet
not mod_NetUsage but are they really different?
Should there or could there be:
mod_aspdotnet.so CPP files ways
(requiring Visual Studio .NET CPP for source code adjustments)
mod_aspdotnet1.so CPP that loads an assembly only
(allowing C# or VB.NET or any of the 50+ languages for source code adjustments)
mod_aspdotnet2.so CPP that test "who knows what later"
There would be three compiled mod_aspdotnet.so CPP zipped files available (or two or five?).
Is this doable?
This would allow for those who only
use the free available tools (no Visual
Studio .NET CPP needed with assemblies but I'm told for the CPP way, Visual Studio .NET
CPP is required due to Apache designs).
Plus using assemblies allows for using AppDomainSetup for the other AppDomains and other such .NET extra calls (Yes CPP can add this too but requires Visual Studio
.NET CPP).
A CPP file is needed to load the CLR,
but after that can it all be done in .NET,
and still keep Apache's pools, and etc. for the larger sites or maybe a different mod_aspdotnet version for smaller sites?
Any thoughts?
Jeff
