Hi Congwu,
On Sep 14, 2009, at 9:15 , Chen, Congwu wrote:
Maybe an approach could be to count consecutive 222 alerts AND also
monitor the real time, and then abort the loop after 5 cycles but
only
if they occur within less than 20 seconds real time.
It'll be great if you can give that a try.
I have implemented here:
http://git.moblin.org/cgit.cgi/libsynthesis/commit/?h=congwu&id=90116491ed28d386f241336ac79e173eb7d9d0ac
Lukas, maybe you can give a review?
Thanks a lot! I modified it slightly (using linertime_t/getSystemNow()
instead of time_t/time() because time() is not supported on all the
platforms we compile the SyncML engine on) and applied to my branch. I
don't have a test provoking the 222 loop, but I verified that it does
not break our current tests.
I pushed it (along with a lot of other stuff and merges from various
moblin contributions) just some minutes ago into a new "luz" branch on
[email protected]:libsynthesis.git. I'll use this new branch from
now on to publish current status of my work ahead of "official"
merging into "master".
Best Regards,
Lukas Zeller ([email protected])
-
Synthesis AG, SyncML Solutions & Sustainable Software Concepts
[email protected], http://www.synthesis.ch
_______________________________________________
os-libsynthesis mailing list
[email protected]
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
