• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: JavaClient offline storage / replication
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JavaClient offline storage / replication


  • Subject: Re: JavaClient offline storage / replication
  • From: Anjo Krank <email@hidden>
  • Date: Thu, 16 Apr 2009 19:44:46 +0200

Heh. The first one has no real mention of conflict resolution in the PDF apart from:

More complex conflict resolution strategies can be accomplished by using the IDataLoaderFilter
extension point which has access to both old and new data.


and the second says: 	

• Conflict detector and resolution – Daffodil Replicator offers very strong conflict detection and resolution functionalities that allow multiple users to send in changes from the workstations simultaneously, while ensuring the integrity of the data. "paste a link to conflict resolution document".

The last part of the sentence is particularly neat :)

Bottom line is you might as well go with the serialized adaptor ops, as these do basically what you can by using these packages.

Cheers, Anjo


Am 16.04.2009 um 18:53 schrieb John Huss:

While googling this, I found a couple interesting projects that may be useful, just in case anyone is interested. I just looked at them briefly.

http://symmetricds.codehaus.org/index.html

http://opensource.replicator.daffodilsw.com/index.html

John

On Thu, Apr 16, 2009 at 6:50 AM, Anjo Krank <email@hidden> wrote:
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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >JavaClient offline storage / replication (From: John Huss <email@hidden>)
 >Re: JavaClient offline storage / replication (From: Stamenkovic Florijan <email@hidden>)
 >Re: JavaClient offline storage / replication (From: Lachlan Deck <email@hidden>)
 >Re: JavaClient offline storage / replication (From: Stamenkovic Florijan <email@hidden>)
 >Re: JavaClient offline storage / replication (From: John Ours <email@hidden>)
 >Re: JavaClient offline storage / replication (From: Anjo Krank <email@hidden>)
 >Re: JavaClient offline storage / replication (From: John Huss <email@hidden>)

  • Prev by Date: Re: [OT] Apache rewrite rule
  • Next by Date: Re: WOWODC West Attendees...
  • Previous by thread: Re: JavaClient offline storage / replication
  • Next by thread: Re: JavaClient offline storage / replication
  • Index(es):
    • Date
    • Thread