Derek and Shawn
THe content repository can store files in the filesystem. Besides that, you can write a CR application that publishes the live content merged with a template under the page root.
I am not sure of the advantages of using CVS to manage the content.
File storage content for postgresql, at least, is already stored in the filesystem under openacs-4/content-repository-files. This actually stores all the revisions under this hierarchy. Its transparent to the user of the site and the developer where the content is stored.
About content based URLs, this is also a good idea. I already wrote a very short index.vuh to be added to file-storage that will present files under the folder hierarchy with their filename, and will not require a revision_id. It always serves the live revision of an item. It can be made to also serve other revisions to file owners with an optional revision_id parameter.
This is a fairly straighforward thing to implement for most packages.
