Thta is not exactly true. They adjust both url filters and handlers registered in urltrie. You can easily enhance fastpath registered proc to take pageroot from arg given to registration and then you can serve static content from virtual host pageroot. You can achive that and even more with my second proposal, ns_url2file_map command which is vserver aware.
I was speaking of the code I have seen, obviously you can write code to handle static content. The fact is you can write code to do it without mucking with the core. However, to adjust pageroot, you would need to modify the core.
Anyway my proposal is not strictly virual hosting solution. It allows some kind of virtual hosting - handling many urlspaces in one server.
Your code is good, I'm not questioning your solution. The issue with virtual hosting is that any two developers will have two different well thought out ways of providing virtual hosting. Making changes to how the core works and changes to the core api (not additions to) is a very heavy handed way of supporting a single virtual hosting solution. AOLserver already fully supports virtual hosting using registered filters and registered procs. The fact that you have to write a few lines of code to tweak that support isn't very important.
But this doesn't solve problem of having no real pageroot. I've got subdirectories in packages (like in OpenACS) that I would like to expose at some URL prefixes. Fixed filesystem layout is essential for application modularity and for code version control with CVS. I have no idea how to manage it the other way.
I guess I don't understand what you can't do. What is the problem of 'no real pageroot'? Since you mention OpenACS, I am guessing that you want to maintain your code in modular packages and 'mount' those at multiple places, creating a virtual filesystem. If that is what you are after, just use the OpenACS rp filter, why modify the core code?
--Tom Jackson
I. To remove yourself from this list:
Send a message to "[EMAIL PROTECTED]" with the following text in the BODY of your message:
signoff aolserver
II. For a complete list of listserv options please visit:
http://listserv.aol.com/
III. For more AOLserver information please visit:
http://www.aolserver.com/
