>>>>> "Peter" == Peter Donald <[EMAIL PROTECTED]> writes:
Peter> ie Consider the following example. When connecting to a
Peter> database and you need to retrieve resources to access
Peter> database from a service directory (whether that be
Peter> ServiceManager, ComponentManager or JNDI Context
Peter> etc).Should you
Peter> a) Store the Connection object in service directory b)
Peter> Store a DataSource in service directory
Peter> Obviously most people are going to say (b) because it
Peter> scales well and is simple to do.
Somehow I feel DataSource is similar to Request that Berin proposes.
Apparently you don't like the idea of embedding such mechanism into
ComponentManager itself for it may foster sloppier design.
Peter> and repeat for all performance sensitive operations. It
Peter> would make cocoon sooo much faster and it would also mean
Peter> we wouldn't have to keep making compromises in core parts
Peter> of Avalon for what I consider to be bad use cases.
I feel that profiling is in order to determine the performance impact
of switching to Request architecture.
Yesterday I realized that String hashing and comparisons (not
construction though) may be of little relevance to performance. Don't
you think synchronization to be a bigger performance drain?
Synchronization is pretty much inevitable in a ComponentManager
implementation isn't it?
I still think the change would be a boon if it reduces code as Berin
demonstrated.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
