Because with HiveMind services, in your code you always deal with proxies. When SessionPropertyPersistenceStrategy calls a mehod on the WebRequest it really calls a proxy which determines the correct instance belonging to the current thread and then, in turn, calls the core implementation itself.
> -----Original Message----- > From: Eric Fesler [mailto:[EMAIL PROTECTED] > Sent: Friday, May 04, 2007 9:24 AM > To: Tapestry users > Subject: SessionPropertyPersistence and Infrastructure object provider > > Hi, > > it's maybe a newbie question but I'm missing something and I > can't understand the following: > > SessionPropertyPersistenceStrategy seems to be a service > deployed as a *singleton*. > It has a property webRequest into which one injects > infrastructure:request. > > How can the SessionPropertyPersistenceStrategy service be > thread safe (and it is ) and at the same time use a property > webRequest that is thread dependent? > > Could somebody provide me some explanations? > > Thanks, > > --ERic > > --------------------------------------------------------------------- > 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]
