[Bug 826] Changed - failure to deal with

bugs@bugs.horde.org bugs@bugs.horde.org
Thu, 27 Dec 2001 20:17:15 -0400


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

*** shadow/826	Thu Dec 27 13:21:36 2001
--- shadow/826.tmp.1885	Thu Dec 27 20:17:15 2001
***************
*** 154,156 ****
--- 154,189 ----
  I'm not sure what you mean by "what the database was expecting" - what 
  database? This is a bit more complicated than a simple SQL frontend app... can 
  you elaborate more on how this would work?
+ 
+ ------- Additional Comments From lindsay-horde@adam.com.au  12/27/01 20:17 -------
+ Firstly, I was involved in administrating the system I was talking about, not 
+ developing it as I'm not a software developer but I'll try to explain anyway as 
+ I've discussed the workings of the system with the developers.
+ 
+ I've confused you when talking about 'what the database was expecting'. I'd had 
+ a very brief glance at the horde_pref table contents and had incorrectly 
+ assumed that it contained session state variables such as the number of 
+ messages in the inbox, sorry about that. 
+ 
+ OK, so instead of making more possibly incorrect assumptions about the workings 
+ of your system I'll just explain how the system I was involved in worked and 
+ hopefully it will be helpful.
+ 
+ With the system I was involved in, one of the problems faced was similar to 
+ what I'm experiencing with Imp which is that if a user submitted a form and 
+ then pressed stop on the web browser then the contents of html form they have 
+ in front of them did not correspond to what was actually in the system.
+ 
+ ...now, hopefully this is what the problem I've experienced with Imp is...if 
+ not just stop reading now and sorry about wasting your time :)
+ 
+ Anyway so the way this was overcome was that when the form was submitted by the 
+ web browser, the form receiving software would take all of the contents of the 
+ form posting and create a checksum from those values. The same thing would then 
+ be done with the relavent contents of the back end database and the two 
+ checksums would be verified.
+ 
+ If the two checksums didn't match then an error page would be generated. 
+ 
+ So, hopefully what I've said is relavent (and I haven't said anything too 
+ stupid) :)