I agree. There are much larger issues that need to be resolved before
discussing implementation details in this forum.
I think it's great that the folks discussing the experimental architecture have
identified areas where VCL can be improved and I would like to find a way for
the community to
I agree with Josh.
To date there has only been a list of "problems" and a diagram. There as
not been much(if any) discussion on the details of the problems mentioned.
The current code base is proven and is doing what it is tasked to do.
Currently it is managing close to a 1000 nodes and supportin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday May 17, 2009, Michael Brown wrote:
> The wiki document for the experimental branch now suggests the use of a
> database abstraction layer. I propose the use of an object relational
> mapper to accomplish this abstraction. This has the advan
The wiki document for the experimental branch now suggests the use of a
database abstraction layer. I propose the use of an object relational
mapper to accomplish this abstraction. This has the advantage of being
extremely easy to use, less code needs to be written, therefore fewer
errors will r
mail.com]
Sent: Thursday, May 14, 2009 4:16 PM
To: vcl-dev@incubator.apache.org
Subject: Re: VCL Experimental Architecture
I agree. Here is a starter list of high level issues:
- architecture modularity
. core
. resource management
. gui/api
. operational metrics and logging
. component templa
e. It causes a fractured community if a few people in the
> community
> decide to redesign large parts of the codebase without having discussions
> about it on this list.
>
> Josh
>
> On Thursday May 14, 2009, Andrew Brown wrote:
> > I've just made a clarification
redesign large parts of the codebase without having discussions
about it on this list.
Josh
On Thursday May 14, 2009, Andrew Brown wrote:
> I've just made a clarification on the vcl experimental architecture
> document:
>
> In regards to the core's frontend API interface
I've just made a clarification on the vcl experimental architecture
document:
In regards to the core's frontend API interface about values including
image_id, ticket_id, and so fourth, the frontend needs to map which resource
manager corresponds to those values, but they may or may not
