Hi. I know a few points, like using LoadableDetachableModel’s to keep session size low. As it has to be replicated in some way between server nodes in a cluster, or stored in a database. Session stickiness is probably how most deployments work.
But what about offloading the session into one or more cookies (which are encrypted) and such. Is that something that is actually being done in practice? It basically would not require session replication in the background and could work without session stickiness. Session size. In middle sized web applications with a JavaScript enabled components. Or actually generally, what is a session size that is ideal, or good to replicate? What is your experience? Regards, Manfred --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
