Hello Patrick,

your analysis is (as always :-) straight to the point - a circular dependency.

I first thought maybe you could run the preflight earlier, but then I found the 
note in binfileimplds saying "Don't call before types are ok (we need 
TSyncItems)". That's the real problem, because checking for changes and 
calculating data CRCs, the preflight needs TSyncItems, and these in turn need 
to be related to a TSyncItemType and these are subject to negotiation during 
sync init.

So I see no easy way to run the preflight earlier :-(

Best Regards,

Lukas


On 21.01.2014, at 16:27, Patrick Ohly <patrick.o...@intel.com> wrote:

> I am wondering about NumberOfChanges information sent from a Synthesis
> client to a Synthesis server. Normally this is not really interesting,
> but in my case the client and server are both running locally and the
> user is actually controlling the server side, so having the client's
> information would be useful in that case.
> 
> What I see is that the client side calls
> TBinfileImplDS::getNumberOfChanges() inside
> TLocalEngineDS::engClientStartOfSyncMessage(). If getNumberOfChanges()
> returned a valid number here, it would get added to the Sync header. But
> TBinfileImplDS does not have a value yet. The value gets computed only
> later, in TBinfileImplDS::changeLogPreflight().
> 
> The engine only calls TBinfileImplDS::getNumberOfChanges() once more for
> local progress events.
> 
> Is there a chance to make the SyncML NumberOfChanges feature work for
> binfile clients? Any idea what change might be needed?
> 
> To me it looks like a circular dependency: DB initialization doesn't
> start unless syncing started, and having the information available when
> syncing starts depends on initialization.
> 
> -- 
> 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.
> 
> 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
os-libsynthesis mailing list
os-libsynthesis@synthesis.ch
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis

Reply via email to