Also, as per the XPM-RPC specs (http://www.xmlrpc.com/spec <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: [email protected] [mailto:[email protected]] On Behalf Of Aggarwal, Ajay Sent: Wednesday, August 12, 2009 4:47 PM To: [email protected] 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. <Task> .... <name>created</name> <value><dateTime.iso8601>20090806T17:52:13Z</dateTime.iso8601></value> </Task> However the Event.timestamp field, which is also of type 'datetime' as per the Xen API specs, comes as integer looking string <Event> ... <name>timestamp</name> <value>1249581133.</value> </Event> I was wondering why. Also what's the dot at the end of that number? -Ajay
_______________________________________________ xen-api mailing list [email protected] http://lists.xensource.com/mailman/listinfo/xen-api
