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: <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-API] question regarding Event.timestamp field
From: "Aggarwal, Ajay" <Ajay.Aggarwal@xxxxxxxxxxx>
Date: Mon, 17 Aug 2009 09:49:13 -0400
Delivery-date: Mon, 17 Aug 2009 06:49:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BC2F8964429F14468EA0E6D6CF00E8C90A5008@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>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcobjgmKNiqvcLQ3Tfipj0dfB6pcKADsdGpg
Thread-topic: [Xen-API] question regarding Event.timestamp field

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.



From: xen-api-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-api-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Aggarwal, Ajay
Sent: Wednesday, August 12, 2009 4:47 PM
To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] question regarding Event.timestamp field


While looking at the traffic between XenCenter and XenServer 5.5,  I see that in all other places such as Task.created, Task.finished, VM.snapshot_time etc., the ‘datetime’ type of field comes on wire as a <dateTime.iso8601> element, e.g.








However the Event.timestamp field, which is also of type ‘datetime’ as per the Xen API specs, comes as integer looking string








I was wondering why. Also what’s the dot at the end of that number?




xen-api mailing list
<Prev in Thread] Current Thread [Next in Thread>