> And now for the reason of this mail: :)
> Win2k Wireless link (irftp) Sends time as the string
> "2000-12-04T16:57:00Z" in unicode. Is this allowed or has MS broken the
> spec? (again)
Your reading of the spec is right, and so it certainly looks like Win2k is
wrong. A few thoughts...
Are you using a final release version of Win2k? I know early beta versions
had a bug where they were sending the time stamp as unicode text. This one
*may* have been fixed too.
They might have written this against the OBEX 1.0 spec, which was very vague
about the exact form of ISO8601 date to use. It was only in 1.2 that the
exact definition was added.
I guess if there's such a thing as a generic ISO8601 parser about, it can't
be wrong to use that. Otherwise, it's either a MS specific bodge, or else
timestamps just won't work with Win2k.
(Note that any 4 byte date stamp support is a IrXfer (Win 95) specific bodge
already!)
Cheers
Jonathan
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Pontus Fuchs
> Sent: 04 December 2000 17:11
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [OBEX] Help! OBEX Time-header
>
>
> Hi!
>
> I need some help on interpreting the time-header (0x44).
>
> Section 2.2.5 (page 16) states that:
>
> "Time is a byte sequence that gives the object's UTC date/time of last
> modification in ISO8601 format. Local times should be represented in the
> format YYYYMMDDTHHMMSS and UTC time in the format YYYYMMDDTHHMMSSZ. The
> letter T delimits the date from the time. UTC time is idenitifed by
> concatenting a "Z" to the end of the sequence. When possible UTC times
> should be used. The Date/Time header is optional"
>
>
> As I understand this, this header shall contain (taking time of writing
> this in sweden (UTC+1) as an example)
>
> "20001204T175700" or "20001204T165700Z"
>
> and nothing else. Further the string shall be in ASCII, and
> null-termination at the end is optional. ISO8601 specifies a lot of
> different formats, but as I understand the OBEX-spec it's pretty clear
> that the two formats above are the only valid.
>
>
> And now for the reason of this mail: :)
> Win2k Wireless link (irftp) Sends time as the string
> "2000-12-04T16:57:00Z" in unicode. Is this allowed or has MS broken the
> spec? (again)
>
> /Pontus Fuchs
> _______________________________________________
> OBEX mailing list
> [EMAIL PROTECTED]
> http://www.pasta.cs.uit.no/mailman/listinfo/obex
>
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
