[Bug 826] Changed - failure to deal with

[bugs@bugs.horde.org]

http://bugs.horde.org/show_bug.cgi?id=826

*** shadow/826	Tue Dec 25 12:02:10 2001
--- shadow/826.tmp.22194	Wed Dec 26 07:58:11 2001
***************
*** 135,137 ****
--- 135,151 ----
  I can't reproduce this. I'm not really surprised that hitting the browser's 
  stop button in the middle of an operation can cause undefined behavior, and I'm 
  not sure how we could possibly trap for it.
+ 
+ ------- Additional Comments From lindsay-horde@adam.com.au  12/26/01 07:58 -------
+ Web based software I've been involved in have used session checksums to help 
+ the backend software understand if something out of the ordinary is happening 
+ and deal with it more gracefully...
+ 
+ As in, just before an action takes place the browser posts a series of values 
+ such as messages in the current folder, messsages read/deleted etc. and a 
+ checksum is created. This is then verified with what the database was expecting 
+ before the requested task is actioned.
+ 
+ I guess this might be a problem on large scale implimentations???
+ 
+ ...is something like that a possibility in this case?