-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Matthieu Chase Heimer wrote: | I'm writing an application that has a mina client and mina server. | Currently I'm developing with Mina version 2 and eventually there will | possibly be non-mina clients. | | How do people handle clients reconnecting after dropped connections when | you have attributes stored in you ioSession on the server side? | | I see the info on this page http://mina.apache.org/faq.html for making a | client reconnect but won't that end up with the reconnected client | getting a different session on the server? | | I'm looking for something like a HttpSession I guess with some type of | session tracking across connections. | | Thanks, | -Chase | |
Hi, One way to track each individual client might be to assign it a client id and have the client submit it as part of your protocol. A simple class for storage/retrieval this might be the use of a ConcurrentHashMap. With the client id you could retrieve your existing attributes, assuming you worked out the details. (e.g: authentication, encryption, removal of long lived client ids, etc.). - -Johnny -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoTBIIACgkQnQTBLXttTeWRLgCeMvnkm8BwNxh6wuPuZIOsXey8 gM4AniCg1G58In+//XShRNIxkLzRKVuz =9/QO -----END PGP SIGNATURE-----
