Antony: I was assuming (given a replication scenario) that I'll be using one node as a master, and spring would only access this node for updates, while the others would be used for reading only.
Sven: This solution would simply throw an exception from spring DAO layer if the object you're trying to update is already being modified by another thread, before even accessing couch - so no need to rollback the intermediate state. Couchdb would also throw exception, if you're trying to modify using an old revision number, as usual. regards, Andrius Juozapaitis >> I wonder if there's really a way to handle this in any transparent way >> (with or without Spring/AOP). >> > > I'm going to bet that it's not possible, if for no other reason than the > lack of a low level interposition mechanism that covers updates generated by > replication. > > Antony Blakey > -------------------------- > CTO, Linkuistics Pty Ltd > Ph: 0438 840 787 > > Reflecting on W.H. Auden's contemplation of 'necessary murders' in the > Spanish Civil War, George Orwell wrote that such amorality was only really > possible, 'if you are the kind of person who is always somewhere else when > the trigger is pulled'. > -- John Birmingham, "Appeasing Jakarta" > > >
