> You could go one step further and send, not an invalidation, but a > replication message. This would contain the Entity's new value and head > off any reloading from the DB at all.... > > All of this needs to be properly integrated with e.g. transactions, > locking etc... > > Perhaps Totem might be useful here ?
Yes, I would decide in this area it would be worth using totem. As I said in a different email, you would have to pick a concurrency control protocol. I favor multi-version 2-phase locking, or multiversion timestamp ordering in the case of transactions that don't mind rolling back.
