Virtual File System
(Difference between revisions)
| Line 1: | Line 1: | ||
| − | Open Cms comes with an own filesystem. Most data like the dynamic pages of the | + | Open Cms comes with an own filesystem. Most data like the dynamic pages of the Opencms [[Workplace]] as well as websites and website [[templates]] are stored in a special filesystem, the so-called Virtual File System (or VFS in short). |
The VFS is completely stored in the database. It has it's own set of access functions, an own, operating-system independent permission model and it knows it's own set of [[Resource|resource]] types. Because the file system is extensible, new custom resource types can be added, without modifying the core routines of opencms. | The VFS is completely stored in the database. It has it's own set of access functions, an own, operating-system independent permission model and it knows it's own set of [[Resource|resource]] types. Because the file system is extensible, new custom resource types can be added, without modifying the core routines of opencms. | ||
Revision as of 13:53, 4 November 2006
Open Cms comes with an own filesystem. Most data like the dynamic pages of the Opencms Workplace as well as websites and website templates are stored in a special filesystem, the so-called Virtual File System (or VFS in short).
The VFS is completely stored in the database. It has it's own set of access functions, an own, operating-system independent permission model and it knows it's own set of resource types. Because the file system is extensible, new custom resource types can be added, without modifying the core routines of opencms.
The Virtual file system cannot be normally accessed on the operating system level (although there are open cms extensions for making it available, e.g. through an FTP service).
