You should remember that HTTPSession usage should be kept to a minimum, especially in a clustered environment. HTTPSession usage doesn't scale well. Do you really need to persist a list in the session? Could you instead just store a user id (or other filter parameter) in the session and look up the list each time it is needed from a service? If you find later that the lookup is expensive, you could look at caching at the service level.
-- View this message in context: http://tapestry.1045711.n5.nabble.com/SelectModelImpl-Non-Serializable-Prevents-Session-Replication-in-Cluster-tp5720280p5720284.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
