[GroupDAV] GroupDAV Connector / Corrupted Times (ZideStorebug?)

[matt]

Are the dates the devices are sending accurate in GMT time?

I had problems with Funambol's parser actually converting time to GMT  
format (with the Z at the end), without actual time conversion, even  
though the devices were sending local time without the Z, so the data  
converter actually treats them as local. It appears, with the UTC  
flag unset, ical4j then (inadvertently) adjusts the time we give it  
forward/backward accordingly.
On 23/01/2007, at 3:51 AM, Chris Bryant wrote:

> I noticed changes to events related to timezones also.  I noticed  
> that events were coming into the Funambol server with the proper  
> start date/time and end date/time, with a Z at the end to indicate  
> GMT time, but when it gets stored on the GroupDAV server, the Z is  
> removed, converting the time to localtime instead.  I assume the  
> GroupDAV connector is making this change, but I don't know if this  
> is being done inadvertantly or intentionally.
>
> Chris
>
>
> ----- Original Message ----- From: "Adam Tauno Williams"  
> <adam@morrison-ind.com>
> To: <groupdav@opengroupware.org>
> Sent: Monday, January 22, 2007 11:26 AM
> Subject: Re: [GroupDAV] GroupDAV Connector / Corrupted Times  
> (ZideStorebug?)
>
>
>> On Mon, 2007-01-22 at 11:20 -0500, Adam Tauno Williams wrote:
>>> On Sat, 2007-01-20 at 10:11 +1100, matt wrote:
>>> > Only the server name and port are required in the URL field,
>>> > everything else goes into server source now, like so:
>>> > http://comalies.citadel.org/~matt/funambol/latest/deployment/
>>> > x97.html#source-create
>>> Excellent;  it is now tossing data back and forth.
>>> Only now I see corrupted times in the OpenGroupware schedular.  An
>>> appointment created on the WinCE device and synced looks like:
>>> Starttime: Tuesday, %Y-%m-%d %H:%M %Z
>>> End Time: Tuesday, %Y-%m-%d %H:%M %Z
>>
>> Arghh.  Nevermind;  everything is the schedular is showing up with  
>> the
>> weird time string.
>>
>>> The appointment does appear on the correct day,  and if I click  
>>> edit I
>>> see a start time of 10:30 and an end time of 12:00.  So the  
>>> duration is
>>> correct.  Appointment on the device was fo 15:30 - 17:00.
>>
>> But the time shifting is still valid.  Does the connector send the  
>> time
>> to the server with a timezone or in GMT?  Because it looked like
>> somewhere along the line 5 hours gets subtracted (and we are in  
>> GMT-5).
>>
>>> Even after I correct the time and save the appointment the time  
>>> appears
>>> as the string above ["%Y-%m-%d %H:%M %Z"].
>>> Title and location are correct.
>>> Seems very odd.
>>
>>
>>
>>
>> -- 
>> GroupDAV
>> groupdav@opengroupware.org
>> http://mail.opengroupware.org/mailman/listinfo/groupdav
>>
>>
>>
>
>
> -- 
> GroupDAV
> groupdav@opengroupware.org
> http://mail.opengroupware.org/mailman/listinfo/groupdav