Forum OpenACS Q&A: Response to Virtual Hosting - OpenACS 3.2.5
The VAT module includes a templating system. Templates are grouped into modules. Currently the module name is the first directory under pageroot. So in http://example.com/ecom/ 'ecom' would be the module name. If you had a script that showed the cart contents, that template would be named 'cart', for instance. if you set this up correctly, then visiting /ecom/cart would run the cart script and template. But the cart ending can be used anywhere under /ecom/, so you could encode the client number into the url just as well: /ecom/client1/cart. I have a simple proc that pulls the variables out of the url, that I have posted to this forum in the past. With this method, you can have one set of scripts and templates for many clients.