Well...there is when you find out that simple persistency solutions may
start being a problem for you. Most of the times is as Joachim says, that
is, the synchronism of data is managed by the persistency solution. Could
be mongo (but I never tried with multiple images), could be Glorp,
GemStone, Ma
Sean,
I guess most guarding is based on optimistic locking these days. But
neither Seaside nor Amber imposes any mechanism on the developer. So you
are on your own there. I have been using TOPLink or Glorp and Seaside
for a few years now, and all I've seen or used so far used optimistic
locki
