This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-API] question regarding Event.timestamp field

To: "'Aggarwal, Ajay'" <Ajay.Aggarwal@xxxxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-API] question regarding Event.timestamp field
From: Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
Date: Mon, 17 Aug 2009 15:21:09 +0100
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Tue, 18 Aug 2009 08:33:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BC2F8964429F14468EA0E6D6CF00E8C90A5019@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <BC2F8964429F14468EA0E6D6CF00E8C90A5008@xxxxxxxxxxxxxxxxxxxxx> <BC2F8964429F14468EA0E6D6CF00E8C90A5019@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcobjgmKNiqvcLQ3Tfipj0dfB6pcKADsdGpgAACXu/A=
Thread-topic: [Xen-API] question regarding Event.timestamp field
Hi Ajay,

Ajay wrote:
> However the Event.timestamp field, which is also of type 'datetime' as per 
> the Xen API 
> specs, comes as integer looking string

Unfortunately this is a mismatch between the spec and the XenServer 
implementation. The trailing dot on the end indicates this is a floating point 
number with an omitted final '0' suffix. The number is a Unix 

> Also, as per the XPM-RPC specs (http://www.xmlrpc.com/spec), the 
> <dateTime.iso8601>
> example is given as "19980717T14:08:55". Note that it does not contain the 
> milliseconds
> and the timezone information.  However looking at the traffic between 
> XenCenter and 
> XenServer 5.5, it looks like they do include the timezone information.

You are correct that the <dateTime.iso8601> elements sent by XenServer contain 
a timezone (always UTC or 'Z'). The intention was to reduce confusion by making 
the timezone explicit. Although different to the XMLRPC example I think this 
still conforms to the ISO8601 spec:



Dave Scott <dave.scott@xxxxxxxxxx>
Senior Architect, Citrix Systems (R&D) Ltd.
[Company #02300071, SL9 ODZ, UK.]

xen-api mailing list

<Prev in Thread] Current Thread [Next in Thread>