[Tickets #11693] Re: Due date / Delay date is not being synchronized with ActiveSync

bugs at horde.org bugs at horde.org
Wed Nov 14 16:51:52 UTC 2012


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

Ticket URL: http://bugs.horde.org/ticket/11693
------------------------------------------------------------------------------
  Ticket             | 11693
  Updated By         | Git Commit <commits at lists.horde.org>
  Summary            | Due date / Delay date is not being synchronized with
                     | ActiveSync
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Git Commit <commits at lists.horde.org> (2012-11-14 16:51) wrote:

Changes have been made in Git (master):

commit a8fad336b1552a8d85078cd2361cd46cab9ad190
Author: Michael J Rubinsky <mrubinsk at horde.org>
Date:   Wed Nov 14 11:45:49 2012 -0500

     Bug: 11693 Some clients require the duedate/startdate fields.

     This makes no sense to me. The protocol docs state the  
POOMTASKS_DUEDATE and
     POOMTASKS_STARTDATE fields are for the "local" time of the  
duedate. While the
     *_UTCSTARTDATE and *_UTC_DUEDATE fields are for the UTC time.  We have
     no way of knowing, on the server, what the local timezone of the  
device is, and
     the device, likewise, has no way of knowing what the server's timezone is.

     Additionally, the docs also state the ALL date/time data are to  
be transmitted
     in UTC. Some devices transmit both fields to the server,  
formatted as UTC time,
     but with the actual time offset by the UTC offset for the devices  
timezone!

     Until someone can provide a better explanation to me, we will  
treat both fields
     as equal.

  nag/lib/Task.php |    6 ++++--
  1 files changed, 4 insertions(+), 2 deletions(-)

http://git.horde.org/horde-git/-/commit/a8fad336b1552a8d85078cd2361cd46cab9ad190





More information about the bugs mailing list