By Date: <-- -->
By Thread: <-- -->

module xml feature request



Jason wrote:

> Nice. That would also be able to handle the synchronisation of files as well 
> as database data.
> 
> It does seem to concentrate on mobile devices though, so I'm wondering 
> whether it is more suited to lots of little updates synchronised between two 
> systems in real-time, more than mass updates performed at the discretion of 
> the administrator?
> 
 From what i know of it, which is not much, the 'initial sync' as it 
is often called when using the mobile devices should be handled by 
syncml implementations. (discovery phase, registering the data boths 
sides can share etc.)
I think it's optimized for batch operation (i.e. you (ir)regularly put 
your pda into the cradle and sync up with the desktop) I think for 
real-time sync its less suited (performance wise) as it assumes 
basically nothing but protocol conformance from both sides. Techniques 
like database replication are more optimized for real-time 
synchronisation and make huge assumptions on both sides (as in, their 
config needs to be done specifically targetting both sides)

Both sides of the equation (possibly one, if defined as the 
'controller' which knows about the state of the other sides it syncs 
with) should probably store sync-state information. (like 'peer 24' 
synced upto 'checkpoint 15' in attention area 'articles')

The concept would imply to expose a xaraya instance as a 'device' 
which offers/accepts updates into several 'attention-areas' (in pda 
like situations these would be events, todos, adresses etc.) The 
obvious mapping here would be to define modules as the main attention 
areas, diversified by their itemtypes; connect both sides through the 
syncml connector and define an API steering the protocol, sending the 
updates in syncml format in both directions, after which the local 
install applies what it received.

I know of one (python) application which did just that, i.e. 
synchronizing N instances of the same application. If needed i can dig 
up the details for it.

marcel
_______________________________________________
Xaraya_devel mailing list
Xaraya_devel (at) xaraya.com
http://xaraya.com/mailman/listinfo/xaraya_devel