[Tickets #10277] Re: ActiveSync Calendar and Tasks not working

bugs at horde.org bugs at horde.org
Mon Jun 27 01:21:01 UTC 2011


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10277
------------------------------------------------------------------------------
  Ticket             | 10277
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | ActiveSync Calendar and Tasks not working
  Queue              | Horde Base
  Version            | 4.0.6
  Type               | Bug
-State              | Assigned
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2011-06-27 01:21) wrote:

Ok. Here is what's happening with TouchDown:

Since it is sending an incorrect command order, the data needed to  
*properly* execute a sync is missing.

Normally, a SYNC is issued that polls for events within the device's  
configured time window. The time this sync is performed is persisted  
so that subsequent PING requests poll for changes only since this last  
sync time. Since the SYNC is never performed, there is no previous  
sync time - so ALL events must be polled. For me, this is close to  
2000 events, so this takes quite some time. When the server timed out,  
it was usually involved in timezone computation since this is also a  
relatively long operation. This led to weird output over wire.  Not  
sure if this is also what is happening to the reporter of the other  
bug or not...

Anyway, with current Git code, sync continues to work perfectly on iOS  
devices, native android, and (if the server does not timeout) with  
TouchDown. Once NitroDesk fixes this issue, this should no longer  
happen.

The result of this is that *all* events for a user are polled during  
the PING (normally, this is limited to polling for changes since the  
last sync/ping time).






More information about the bugs mailing list