On Mi, 2010-01-27 at 16:44 +0000, Lukas Zeller wrote: > What about <datastoreinitscript> or maybe <initscript>? These are > called before user data is accessed the first time, which would be > early enough to stop the whole thing if needed, but late enough to be > sure the sync mode is known. BTW: I realized that a useful document > was missing in the docs so far - see my latest commit 9dc1e5c1a3 (Doc: > useful table showing the call flow of scripts within a server session) > on the luz branch.
Have not looked at that document, but it was definitely dearly missing before ;-) > What's currently missing would be some DS-level functions to query the > sync mode, but that'll be simple to add (probably in customimplds.cpp, > within TCustomDSfuncs). To differentiate unwanted from > client-requested slow sync, we'd probably need two of them, like > ALERTEDMODE and ACTUALMODE. Some functions along this line already > exist, I'd have to check to make sure we don't duplicate stuff. Because we can generate the script dynamically, we can enable the test only when needed. So all that we would need is the actual mode. > What I don't really get is why the server would want to modify the > client behaviour other than switching to slow sync (for two-way alert) > or to refresh (for a one-way), which it already does. The server wouldn't do it automatically. It would stop and ask the user how to proceed - this is our "personal SyncML server" which has a GUI. -- 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
