Hi everybody!

I was just wondering how is Tapestry handling concurrent users asking for
the same page (which I understand, is a singleton) where each user has a
different value for a single persistent property (@Persist)

As far as I debbuged, I saw a PropertyConduit in the middle, I suppose it
is put over the field access and it is the responsible for getting and
setting the actual value for each case/user/thread... but my question is
HOW? how (or where) is it implemented?

Best Regards,
Matias.

Reply via email to