Occasionally Connected Application scenario. Is it supported?

After watching telerik tv -openaccess disconnected API- I was wondering if the folowing scenario would be viable:

3 databases on 3 workstations should be in sync. Say we have a customer table, all customers should be available on all workstations.
There is no 'master' database to sync with, they should sync with each other. I guess the first active workstation should take te lead, when a second one comes online it checks for a available 'first online companion' and syncs with it.
In effect all clients sync with one 'lead' workstation.
The application is used offline (local database no network 'in the field') and online (local lan) when users meet to exchange their data (customers and related data)

An added requirement:
The workstation database would be SQL Express 2008 R2.

My first guess would be getting a changeset from the first 'parent' database, and attach this changeset to the second 'child' database and then do the exact same thing reverse: get a changeset from the child and attach it to the parent.
Is it possible? Is it even the way to go or are there better ways to get the same result (using OA or any other tecnique)

I've looked into MS Sync framework too. Though the prefered local database (when using a wizard ;)) is sqlce, syncing sql express databases is certainly possible. However, since we are considering moving from EF to OA, it would be preferrable to solve this problem -or 'challenge'- with OA.

Kind regards,
Alex

Hi Lextendo,

I am afraid that you will not be able to achieve this functionality with the ObjectContainer class. The object container is used to carry persistent object and track their changes in cases when the database is not available. What you want to do is create a changeset with the differences between two databases, which is completely different functionality that unfortunately we do not provide at the moment.
You will either have to manually read the last inserted/updated/deleted objects and synchronize the databases or use a third party synchronization framework.

All the best,
Alexander
the Telerik team