answered 2020-06-23 13:53:03 +0800

cor3000
5250 ● 2 ● 7

seems you already asked the right question in https://forum.zkoss.org/question/112434/serializablesession/

After that you'll likely run into follow-up issues (in case you want to configure clustering), using the default redis session repository.

1. ZK can only work reliably if you use "sticky" sessions in your cluster.

2. ZK will only be able to synchronize concurrent requests to a session when the session returned by your session repository is the same instance. A deserialized session for every request will eventually result in missing components and component state. (A custom session repository implementation is necessary most likely)

3. ZK sessions can become quite big (in complex applications) so that eager session replication is likely to cause significant performance overhead (goes hand in hand with 2)

depending on your goals to integrate with redis you might not be able to achieve all of them ...

Since this is a rather complicated and individual topic this forum might not provide all the detailed answers you need. If that's the case please contact our support for dedicated assistance.