Hi Barry, I'm not sure you understand a Thread Local, it's guaranteed to be
thread safe since it's local to a thread
I would appreciate it if a tapestry committer could chime in with their
thoughts.
Thanks,
Lance
On 22 Mar 2013 20:52, "Barry Books" <trs...@gmail.com> wrote:
> The method is isInvariant so returning false means the value can
> change. This is confusing and it seems like a double negative to me.
>
> public boolean isInvariant() {
> return false;
> }
>
> The set method is commented out because setting the value would affect
> other instances of the component. After thinking about it I'm not sure
> this is as complicated as it seems but I'm a bit fuzzy on the details
> of Parameters. I believe they are really conduits so calling the set
> method in the component calls the set method on all variables bound to
> the parameter. In the case of the default value I don't care if the
> set method is called so I just ignore it. The set method is still
> called on all the other values bound to the parameter.
>
> I don't think ThreadLocal would work if there is a thread pool. In
> that case setting the value would affect all subsequent request using
> that thread.
>
> At any rate it does seem to work with the simple test case I wrote. I
> just wonder if it really is this easy or am I breaking something.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
