On Fr, 2010-02-12 at 17:14 +0000, Lukas Zeller wrote: > > The only solution I see is to make the subdatastore URI's more complex: > > instead of <foo>, let's use <foo:uri> where "foo" is the name of the > > superdatastore and "uri" its remote URI. > > Makes sense. Just a cosmetic thought: why not <foo>uri, so the "real" > remote URI would still be on the same syntax level as for other > datastores, whereas the angle bracket serves as a prefix container for > options to treat that URI differently locally.
I already have it working in SyncEvolution and libsynthesis with the <foo:uri> syntax, see the libsynthesis "superdatastore" branch. There are open questions anyway, so I can change the syntax in the next revision. Can you check whether the changes in the "superdatastore" make sense to you? I ran several tests with SyncEvolution as client and server, including sending changes back and forth. Slow sync detection works as intended. I haven't tested suspended syncs, which may be relevant because one change is about the local map storage. The only problem that I am currently aware of is that after a failed authentication, the second attempt with updated nonce fails because of the fAsSubDatastoreOf check in TLocalEngineDS::engPrepareClientSyncAlert() - see commit message for details. I'm wondering whether not setting fAsSubDatastoreOf in TLocalEngineDS::engPrepareClientSyncAlert() would work better, provided that we prevent sending the <Alert> via some other means, like a check for the special URI. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
