Hi Eran, > An apache module will hide this kind of functionality from > the user. An HttpModule must be registered in the web.config > file, thus forcing every application that needs to handle > this to add that line. > > Putting this code at the Apache module level removes the need > to add the configuration to the web.config file. > After all, it seems logical that in Windows almost no one > will use it and if they do it will be in a very different way. > > Why make them some extra job of removing lines from the web.config? > After all, it is not imperative to have such functionality in > Windows (even on Apache on Windows).
I'm not sure on that, I think there is solutions out there that would like to have that on Windows to. I have made IIS Filters to fix that before for customers. > I think that it is important to implement multiple paths per > Application Host. This kind of behavior will probably be > required by users that will be familiar with IIS 6. I don't think so. IIS 6 has multiple Application Hosts (one per running application) in an farm. We should support the same kind of functionality but it's a lot of work to construct that for Apache but it will bring Apache to the same level as IIS 6 when it comes to application isolation. > It might also be necessary to allow the host to run on a > different user (if this it is possible). For enhanced > security we will need to run the host on different > credentials so the Application Host we have very limited > access to resources. Again, there is a lot of work to create this kind of isolation but when it's done you can easily support running each app host with different users. Cheers, Patrik _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
