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
locking provided by the persistency mechanism.
No doubt you can use JS and Ajax or even WebSockets to make the
round-trip feel more responsive. But there still is the risk of the gap
between some JS request being answered (can these objects be updated?)
and the actual attempt to update. So you basically would do a full round
trip anyways (dear server, update these objects if possible!). It
depends on your taste if that is any better than just using a normal
round trip, like in Seaside. An additional problem could be that you
need to handle objects on the client, which you typically don't in
Seaside, which only renders pages down to the client.
HTH
Joachim
Am 04.08.15 um 12:54 schrieb Sean P. DeNigris:
When using any tool that exposes objects outside the image - Seaside, Amber,
rST - how does one guard against simultaneous edits? Up until now, I've been
perfectly content with single images and read-only web apps, but now that
I'm considering some stateful web apps/services, I can't remember ever
seeing locking addressed. And I wonder if all the cool new JS technology
could make the process more responsive i.e. notify the client if the
underlying data has changed...
-----
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Sharing-Inter-image-Data-tp4840912.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
--
-----------------------------------------------------------------------
Objektfabrik Joachim Tuchel mailto:jtuc...@objektfabrik.de
Fliederweg 1 http://www.objektfabrik.de
D-71640 Ludwigsburg http://joachimtuchel.wordpress.com
Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1
