31-Jul-2006 (update)

WASD
Well, it works - using IP address in stead of name. Thought so! As long as things are kept apart, that is:
In HTTP$CONFIG I specified:

[Service]
http://192.168.0.11:82 for www.grootersnet.nl
http://192.168.0.12:82 for homedesk.grootersnet.nl
http://192.168.0.13:82 for webmail.grootersnet.nl
http://192.168.0.200:82 for anything else (for the time being)

and in httpd$map, I specified a mapping file for each of them:

# www.grootersnet.nl
[Includefile] ht_root:[local]www_grootersnet_nl.conf
# homedesk.grootersnet.nl
[Includefile] ht_root:[local]homedesk_grootersnet_nl.conf
# webmail.grootersnet.nl
[Includefile] ht_root:[local]webmail_grootersnet_nl.conf
# wasd.grootersnet.nl
[Includefile] ht_root:[local]wasd_grootersnet_nl.conf

each of the giving the required mapping like this:

#[[www.grootersnet.nl:82]]
[[192.168.0.11:82]]

pass /* /web_disk2/public/*
pass / /web_disk2/public/

set * map=root=/web_disk2/public/

Not yet complete since scripting directories are currently missing (causing the counter (wwwcount.exe) on these pages to fail) but everthing else seems to be working - once file protection has been set correctly:

$ set sec/acl=(id=HTTP$SERVER,access=EXECUTE+read) web_disk2:[public...]*.*;*

Same applies to the other directories.

Even with this minimal configuration, the increase in speed is VERY NOTICABLE.

Next, getting everything to work this way, including scripting. Stay tuned!