more on ListEditMap

[Jonathan Locke <jo...@muppetlabs.com>]

after more reflection, i think ListEditMap's shortcoming is not so much 
what it is, as the implication in the book that it solves "the back 
button problem" /fully/.  it really only solves the presentation layer 
part of the problem (matching form fields to server side state). 

a good fix for this in the 3.1 version of the book might be another 
section about database integrity that explains how to finish solving the 
back button problem using optimistic locking in the persistence layer.  
for now, even a footnote about this being out of the scope of the book 
in the next printing would be helpful to readers trying to grapple with 
the back button as a problem.  finally, maybe in 3.1, the virtual 
library example could actually do optimisitic locking as an example so 
the whole application has end-to-end data integrity.  that would be 
cool.  make sense?

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org