On Do, 2010-02-11 at 19:50 +0000, Patrick Ohly wrote: [no target for superdatastore] > 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.
I'm going with that and have syncs running, albeit with some problems. One problem is that the client always forces a slow sync for the superdatastore. That's because of the following line in TLocalEngineDS::engPrepareClientSyncAlert(): // check if we are forced to slowsync (otherwise, fSlowSync is pre-set from dsSetClientSyncParams() fSlowSync = fSlowSync || fLastLocalAnchor.empty() || fFirstTimeSync; fSlowSync is false, the anchor empty, fFirstTimeSync false. How should anchor handling work for a superdatastore? -- 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 os-libsynthesis@synthesis.ch http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
