Peter Donald wrote:
On Thu, 5 Dec 2002 13:48, Adam Murdoch wrote:
[...]
I see an interface called Context, with a method that makes me take an Object by giving a key.I dunno. They are precisely the sort of things I draw on when thinking about it :)Honestly, MailetContext and ServletContext were always just noise. There's nothing in common between these and framework's Context except the word 'Context' in their names, and the fact that they each deliver a subset of the resources used by components.
When I think about a context in general, as I have explained in a previous mail, I have in mind threadContexts (*).
"Because Interceptors are stateless, information about the state of the call then must be added to the context of the calling thread. So all of the information is piggybacked on the thread context, and each Interceptor can read, add, change, or remove data from the thread context. Figure 1 is a simple diagram of an Interceptor Stack embedded in a container like, in JBoss, the EJB Container."
http://www.onjava.com/onjava/2002/07/24/graphics/jboss_image002.gif
Actually these per-thread contexts are no different from global context for the user, thus I define them simply as contexts.
I agree that this notion is not exactly that of the current Context interface, since it has the notion of putting stuff on the Context, which is not present.
(*)http://www.onjava.com/pub/a/onjava/2002/07/24/jboss_stack.html
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
