I'm trying to help a Life Balance customer who is using Exchange
ActiveSync to wirelessly sync his TX calendar to work. When the
customer uses both the EAS conduit and our Life Balance conduit at the
same time, the EAS conduit goes into a very slow mode (12-14 minutes in
his case) where it seems to re-copy the entire Exchange calendar
database to the TX. If the Life Balance conduit is disabled, EAS
behaves normally. I'm trying to understand what the Life Balance
conduit might be doing that would trigger this behavior in EAS.
Our conduit syncs both to our four Life Balance databases, and to the
built-in calendar database. For the calendar database, we do not rely
on dirty bits, since we know that these are used by the calendar
conduit. Instead, we use CRCs in our own database to identify modified
records. Any records that our conduit modifies in the calendar database
are marked dirty, just as if the user had modified them manually.
This scheme has been working fine for years, and has been compatible
with the Date Book and Calendar conduits, PocketMirror, IntelliSync,
Apple's iSync conduit, and the Mark/Space event conduit. Why is it
causing trouble with Exchange ActiveSync, and what can we do about it?
(Sorry for not posting this to conduit-dev, but this forum seems much
more active.)
--Stuart A. Malone
Llamagraphics, Inc.
http://www.llamagraphics.com/
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
