Thanks for the reply. Sorry, perhaps I was not completely clear. The context code itself is already written.
I was more unclear as to what is the best way to go about ensuring that a request coming into my Avalon components gets bound with a context. Even in XForge, I needed to do something like: VariablesBroker broker = VariablesBroker.getBroker(); ThreadContext threadContext = new ThreadContext(); broker.startContextScope( threadContext ); ... broker.endContextScope( threadContext ); So my question is: What is the best way in Avalon to ensure that the above startContextScope() and endContextScope() methods get called at appropriate moments? Also, since the containing environment maybe multi-threaded (like an app server), what is the best way to maintain a context-identifier correalation to a given client? I guess maybe what I was looking for is the concept of a Front-Controller from the MVC world or the RequestProcessor concept JBoss used to have. Basically something which allows me perform pre-processing (and hopefully post-processing also) on each incoming request. ----- Original Message ----- From: "Ulrich Mayring" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 27, 2003 3:40 AM Subject: Re: thread contexts > Steve Ebersole wrote: > > [Sessions] > > Look at http://xforge.sourceforge.net/variablesbroker.html for an > example concept. For example code, download X:Forge. > > Ulrich > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
