On Mon, 18 Feb 2002 00:43, Leo Sutic wrote:
> > The CM is just a facade about the underlying store in the
> > container - you can
> > provide whatever mechanisms you want by putting a lil logic in the CM.
>
> But then it is as I said - the CM is the container, and the request must
> come in through the CM. Then the container isa CM, not container hasa CM.
hmmm? I am not sure how you got to this conclusion. Have you lookd at the
phoenix code?
> > public doThis( Request r ) {
> > ((DBConnection)r.getComponentManager().lookup( DBConnection.ROLE
> > )).x(); }
>
> Ugly - requires a framework-level Request object and different interfaces
> for static/per-request usage for each component.
You mean that separate concerns are separated ? Fancy that!
--
Cheers,
Pete
----------------------------------
Ancient Go proverb: "Only amateurs
try to come up with 'fancy' moves"
----------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
