> Yes, this is the point. > > But we could say that the "per request" stuff should not be in > context... but then where?
That is application specific. You have to understand the difference between a global context and a request context. A global context has values that do not change for the life of the context object. A request context passes values that are specific to the context. It is passed in to the method like this: Cocoon.process(RequestContext, true); > Also, we are talking about 1 container, but cocoon is a > container in a container. Heirarchical containers are very valuable, and they help provide scope to components. > Cocoon handles per request, creates Components and assembles them per > request, unlike Phoenix... I'm sure I miss something here, > but it's so > elusive... It *should not* create components per request. It should only *use* components per request--which is closer to the truth. Cocoon creates components when they are are SingleThreaded/poolable and there are no available components to reuse. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
