You could probably also serialize Adaptor ops that occur after
ec.saveChanges() using sth like the ERXAdaptorOperationWrapper and
have some custom code dealing with conflicts. At least this would
allow you to handle things in code, not in SQL.
Cheers, Anjo
Am 16.04.2009 um 04:44 schrieb John Ours:
My main concern with trying this with WebObjects would be, as others
have said, trying to sync the persistence layers. Even if you could
get it to work it would be horribly inefficient. In every system
we've ever built like this we've handled the data sync at the
database level through either OTS or custom replication.
Hypothetically this approach should work with WO...the clients
always write locally and the sync is database-to-database whenever a
connection becomes available.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
