On Tue, 2009-12-15 at 17:10 +0000, Patrick Ohly wrote: > But when both datastores are told to do an unexpected slow sync, then > only the first <alertscript> is executed, then the whole session is > taken down immediately because of the ABORTSESSION() in it. For the > second datastore I end up with the overall session status code instead > of detecting the unexpected slow sync.
I found a solution: I notify the UI that a datastore wants to abort by setting a session variable, then abort there after processing the complete SyncML message. This typically lets me process all Alerts for a client before aborting the session. I still don't have a solution for the server side. See "intelligent handling of unexpected slow syncs" http://bugzilla.moblin.org/show_bug.cgi?id=2416 -- 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
