Hi,
a timeout listener (UserTimeoutListener) can be registered at the
server side to catch lost client connections. It can be registered to
the UserActivityScheduler which can be got from the UserManager
(UserManagerFactory#getInstance#getUserManager()). That was already
described here:
http://groups.google.com/group/gwteventservice/browse_thread/thread/0b19af8990ab2ae8
We will improve the documentation at this point.
At the moment the using applications have to do the user mapping. You
could take a look at the DemoConversationApp, but the user mapping is
solved via an abstract event (upper class) instead of a server-side
user mapping. That is also working for lost connections because the
triggered UnlistenEvent contains the user mapping.
I hope the user mapping doesn't make many difficulties for your
application.
Regards,
Sven S.