the best way is to first show a confirmation screen ( are you sure kinda thingy ) .....
and hey list .... is there a way to check if the client has a connection or he/she has closed the connection using the stop button ..... Guru -----Original Message----- From: Neel Narayan [mailto:[EMAIL PROTECTED]] Sent: 08 October 2002 00:10 To: [EMAIL PROTECTED] Subject: Clients that disconnect after inovking a servlet What should be the servlet behavior when clients close the connection after invoking a servlet? I ask this question more from the perspective of the "right way to handle it" as opposed to the Servlet specification. Let's say a client has invoked a servlet that opens a DB transaction and then hits the stop button on the browser. This causes the connection to end. The user intent here is to prevent the transaction from happening - but the servlet of course does not know this and commits the transaction and will realize that the connection is broken when it's time to respond. How is this problem typically handled? Should I continuously check to see if the connection is alive? Please comment. Thanks, Neela ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
