[Pharo-users] Sharing Inter-image Data

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.