Hi John, Checking the log is definitely a possibility.
Are you using an OutputRepresentation subclass? If so, in your write(OutputStream) method, you should be able to catch an IOException if you can't write anymore and clean-up what you want. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : John.Smith [mailto:[email protected]] Envoyé : vendredi 7 août 2009 10:51 À : [email protected] Objet : RE: Detecting client's disconnection Hi, Thanks a lot for for your suggestions, but I'm afraid the ticket pattern isn't a solution in this case. The 'permanent' connection I was talking about, indicates whether client is active or has crashed. The server should have the information about the client's status as soon as possible. I'd like also to avoid situation where all clients send regular messages indicating that they are still alive. So I guess there is no way to for example set up a listener for the restlet engine exceptions? Should I check the logger for that kind of information? Best regards jgs -- View this message in context: http://n2.nabble.com/Detecting-client%27s-disconnection-tp3325009p3403097.ht ml Sent from the Restlet Discuss mailing list archive at Nabble.com. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=23812 21 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2384443
