I propose exploring an alternative VCL architecture through an experimental code branch at Apache.org. This code would be housed in the svn at apache.org as a branch, and would be explored/developed in parallel with the current 2.X branch. The purpose of this branch is to explore a VCL architecture that allows the following:

To allow VCL manage fluid resources (virtualized) more effectively
Increase modularity by decoupling VCL components from a single, monolithic database via APIs
Manage storage resources
Create a database abstraction layer
Increase image library confidentiality and integrity

I've put a first-pass design document on the apache VCL wiki which outlines the architecture proposed with some level of detail. That document is located here: http://cwiki.apache.org/confluence/display/VCL/Experimental+VCL+Architecture+Document

I'd like feedback of all kinds from the Apache VCL community to explore the architecture's merits and challenges at both the architectural and implementation levels.


Brian Bouterse
Secure Open Systems Initiative

Reply via email to