-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I know the mechanics of @Persist and Session State. But I am looking for advice on how to deal with some common challenges using Tapestry:
* Let's say a page stores stuff in the HttpSession using @Persist - directly or e.g. through use of the Grid component. Whenever a user opens that page twice in different browser tabs, those two instances share server side state, and sorting one of the grids by name can affect the other. * There can be (rare but tricky) race conditions if two AJAX calls are fired concurrently and operate on session data - all of a sudden there is multithreaded logic in the server. These are fairly common but pretty tricky issues. I know @Persist has a configurable strategy for storing state that can be used to store stuff in the browser, avoiding session use completely. But does Tapestry provide support for dealing with these issues when actually storing stuff in the HttpSession? Thanks - - Arno -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+nyVgACgkQbmZsMyUPuXRiFgCfUPbEyZyxpz1+JTDz/hGzMSWC Dw8Ani8Dr/3uIQJp+nOJ12OYuWWFhxks =yDKR -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
