I'm giving my own viewpoint - from outside the group working on the
architecture - but I do have some experience with software projects.
Brian writes:
> This cloud proposal is new and different, and it will redesign and
> likely recode the existing VCL core. Although it seems different,
This cloud proposal is new and different, and it will redesign and
likely recode the existing VCL core. Although it seems different,
this experimental architecture is designed to accommodate the current
roadmap through a different architecture implementation. The
fundamental assumption is
Hi Brian,
I have some additional concerns.
Don't take this the wrong way, it's great to think ahead, but I not sure
this is the right time for such a major proposal.
As you know the apache VCL project is still in incubation stage and we're
struggling to get off the ground, grow the community
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian,
I haven't finished reading through all of the details in the document you
created in the wiki, but it seems to be a design document for a new/different
cloud system. I didn't see anything explaining how it relates to VCL in its
current form
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 ar
