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


[Xen-API] question regarding Event.timestamp field

To: <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-API] question regarding Event.timestamp field
From: "Aggarwal, Ajay" <Ajay.Aggarwal@xxxxxxxxxxx>
Date: Wed, 12 Aug 2009 16:46:59 -0400
Delivery-date: Wed, 12 Aug 2009 13:47:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcobjgmKNiqvcLQ3Tfipj0dfB6pcKA==
Thread-topic: 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>