How are virtualized websites related to virtualized content in the AVM?
The AVM is a very general-purpose content repository; some of its features are being used to support web content management (WCM), but it is capable of performing many other tasks. For example, we plan to create default configurations that will be suited to the needs of source code management (SCM). In WCM, every virtual repository (aka: “store”) contains a top-level directory named “www”. By default, the “www” directory of “main store” of each author and workflow sandbox is just a transparent overlay on the “www” directory of the corresponding staging sandbox’s “main store”. The Tomcat-based virtualization server transforms the virtualized webapp files in the AVM into a set of name-mangled virtual webapps. If you’re curious, you can see some of this in action if you look at virtualization server’s “work” directory.
