Re: Pim toSerialFormat writes the current time and date

this also happens using the fromSerialFormat() method.

Ken Walker wrote:
>
> All I'm saying is that the format of the date in the vCalendar entry
> may be modified by the particular implementation, and it's something
> to look at to see if it matches what you would get in
> System.currentTimeMillis().
>
> /**
> @author Ken Walker, J9 Embedded Java Class Library Manager, IBM Ottawa Lab
> @see http://www.ibm.com/software/ca/en/ottawalab
> @return [email protected]
> */
>
>
>
> *Ian Strain <[email protected]>*
> Sent by: A mailing list for KVM discussion <[email protected]>
>
> 09/14/2007 04:23 AM
> Please respond to
> A mailing list for KVM discussion <[email protected]>
>
>
>
> To
>       [email protected]
> cc
>
> Subject
>       Re: Pim toSerialFormat writes the current time and date
>
>
>
>
>
>
>
>
>
> I don't understand you answer. Are you saying that the method
> toSerialFormat() while reading the pim data changes the scheduled date
> to the current time zone? Why would this be? I was under the
> impression that this method simply takes the pim data and writes it to
> a stream.
>
> I did some more testing, it appears to only happen on Nokia devices.
> The phones I have tested on so far are the Sony Ericsson K750, W850
> and Nokia 6230i, 6131. There was no change to the tasks on the Sony
> Ericsson devices.
>
> Ken Walker wrote:
>
> The current PIM specification states:
>
> "Data type indicating data is a Date in long primitive data type
> format expressed in the same long value format as java.util.Date,
> which is milliseconds since the epoch (00:00:00 GMT, January 1, 1970)."
>
> The differences in the phone (and/or the Java implementation on that
> phone) and the server may be what they consider the current timezone
> to be.   A lot of Java ME implementations ONLY return GMT times and
> don't look at all at the actual current timezone of the phone.
>
> /**
> @author Ken Walker, J9 Embedded Java Class Library Manager, IBM Ottawa Lab
> @see _http://www.ibm.com/software/ca/en/ottawalab_
> @return [email protected]_ <mailto:[email protected]>
> */
>
>
> *Ian Strain **_<[email protected]>_* <mailto:[email protected]>
> Sent by: A mailing list for KVM discussion
> _<[email protected]>_ <mailto:[email protected]>
>
> 09/13/2007 10:28 AM
> Please respond to
> A mailing list for KVM discussion _<[email protected]>_
> <mailto:[email protected]>
>
>
> To
>       [email protected]_ <mailto:[email protected]>
> cc
>
> Subject
>       Pim toSerialFormat writes the current time and date
>
>
>
>
>
>
>
>
>
>
>
> Hi all,
>
> I am writing an app that gets the PIM data from the phone and sends it
> to a
> server. To do this I use PIM.toSerialFormat() that will write data PIM
> entry
> to an output stream which I then send to the server. I then can
> retrieve the
> PIM data at a later late from the server and write it to the phone.
> This all
> works fine.
> The problem is that when I get the PIM data from the todo list (and
> possibly
> the event list, I haven't checked) and write it to the output stream the
> date that was for the todo task changes to the current time and date
> of the
> phone. So therefore when I read the todo task back from the server it will
> have the wrong scheduled time.
>
> For example;
> I have a todo task scheduled to go off on the 20-9-07 at 20:00. When I
> send
> the todo task to the server the scheduled time changes to the time and
> date
> the device is currently at, say 13-9-07 14:53. So when I get the data back
> from the server and save the todo task on the device the time for the
> scheduled task is now 13-9-07 14:53
>
> Has anyone noticed this? Is there a work around? I really hope this is
> not a
> bug in the PIM api. I think it is a serious one!
> At the moment I think the only work round would be to read from the pim
> entry and not us toSerialFormat
>
> ===========================================================================
> To unsubscribe, send email to [email protected]_
> <mailto:[email protected]> and include in the body
> of the message "signoff KVM-INTEREST".  For general help, send email to_
> [email protected]_ <mailto:[email protected]> and include in
> the body of the message "help".
>
> ===========================================================================
> To unsubscribe, send email to [email protected]_
> <mailto:[email protected]> and include in the body of the message
> "signoff KVM-INTEREST". For general help, send email to
> [email protected]_ <mailto:[email protected]> and include in
> the body of the message "help".
> ===========================================================================
> To unsubscribe, send email to [email protected] and include in the
> body of the message "signoff KVM-INTEREST". For general help, send
> email to [email protected] and include in the body of the message
> "help".
> ===========================================================================
> To unsubscribe, send email to [email protected] and include in the
> body of the message "signoff KVM-INTEREST". For general help, send
> email to [email protected] and include in the body of the message
> "help".

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff KVM-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".