Hi, I have done a lot of work over the last few days putting together a major new architectural framework proposal.
It is documented here: http://www.officevision.com/pub/p5ee/software/htdocs/P5EEx/Blue/ Basically, it lays out a component model for P5EE: Context Config Serializer Service Security Templates Messaging Repository Widget Log Each one of the components essentially represents an interface (or abstract class, or a base class with default functionality) which can be implemented using any of a number of physical implementation classes. For a quick overview of the whole scheme, go into each component's page and go immediately down to the "Class Group: <Component>" section. This will give you a good idea of what possible implementations for each component that I have envisioned already. Of course I am interested in feedback. I am eager to move out of the "random posts to the list about your favorite technology" phase to the "let's hammer out an API" phase. But that can't happen until we reach some agreement on how to organize that all technically. If some people think it's great but not most, I would welcome you to join me in building up the P5EEx::Blue namespace. That's what the experimental areas are for: proving ideas. Stephen P.S. All of the documentation was created in POD in order to communicate in the same basic way that Javadoc does. Meanwhile, the data is reasonably structured so that it may be parsed out by some future tool. P.P.S. Happy Thanksgiving for all in the USA.
