Remember that every session has its own copy of Visit, so the only problems you would have would be created by a _single user_ accessing Visit from more than one thread. That could happen, but it would involve either multiple pages being accessed concurrently or someone being click-happy. Either way, they should maybe expect to get nonsense.
Hmm. I myself often open more than one window from the same session; with Amazon for example. I never expect to get nonsense.
I am not completely sure, but it seems that working with more than one browser window and a very slow modem connection makes this more likely to happen. If it takes 10-20 seconds to load a page, it is very conceivable that the user might click more than once in different windows.
Plus, getting nonsense is just one possibility. Who knows what else could happen - data corruption, exceptions. Deliberate denial of service attacks ??
Once the possibility for a problem exists, even though it is under what we think are very rare circumstances, nothing is certain anymore.
Anyway, I think I got my answer. The application should provide synchronization for the visit object, if this is considered a problem. Whether it is a problem depends on perspective.
Thanks a lot to everybody who responded. I am a Tapestry newbie so perhaps I will be picking your brains more in the coming weeks ! :-)
regards, Tzvetan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
