Hi, You might find the following article helpful:
http://benramsey.com/archives/http-status-201-created-vs-202-accepted/ In general, I think a REST API might handle your situation (a request that cannot complete immediately) by returning 202 Accepted, along with either body content or a Location header that points to a new resource location, which the client would then periodically poll until the long-running request was completed. I could be wrong, though... Steve On Sat, Jul 25, 2009 at 6:45 AM, John.Smith <john.garner.sm...@gmail.com>wrote: > Hi, > I was searching the web back and forth and i didn't find a solution to the > following problem (bear in mind that I'm making my first steps in Restlet). > Client makes a request and the computation of the response is suspended > untill another event occures. If the client disconnects when the > computation > is suspended the IO/Socket Exception is thrown. How can > I handle such situation, so I can for instance clear some data structures > hold for this client? > > Best regards > jgs > > -- > View this message in context: > http://n2.nabble.com/Detecting-client%27s-disconnection-tp3325009p3325009.html > Sent from the Restlet Discuss mailing list archive at Nabble.com. > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2375504 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2376159
