Thursday, January 23, 2003

ASP.NET on Apache Apache to support ASP.NET as a module. The linked article characterizes this development as a "thaw" in MS/OS relations. Fictional legal entity relationships aside, the future ramifications for Apache, IIS and ASP.NET might be: There's something to the ASP.NET module that will require Apache to run on a Windows system. Some people have suggested ASP.NET is completely divorcable from IIS, but can it be divorced from the Window platform (practically)? If not, then ASP.NET apps will always need to ruin on Windows systems, and the difference to overall system management and behavior between IIS and Apache deployment won't be significant. ASP.NET and Windows can be completely divorced, and Apache may take off as a real ASP.NET target platform. It is taking a while for J2EE/Servlet developers to realize the development platform can be completely different than the deployment platform, and I suspect the same will happen in the ASP.NET space. Visual Studio.NET is no doubt worlds ahead of any other ASP.NET development platform, and projects will initially tend to favor IIS as a deployment platform. But eventually Apache (Windows or Linux) could become a significant target platform for ASP.NET applications if performance, price or manageability make Apache more attractive than IIS. 11:07:00 AM    comment []