API Change: Timestamps returned from the Reports methods now in include time zone

In our latest update to the API, we decided to make a change in the way timestamps are returned. Previously, a call to Reports_Transactional_GetOpens_String for instance might return data like this:

example_address@nowhere.com
75.149.211.42
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;)
09/14/2011 4:26:00PM

That's OK... but what timezone is that? The time being returned is ambiguous. Is that in the user's local time? JangoMail time? Furthermore, the timestamp is formatted as per the custom in the US - not very good for our international customers.

Therefore, we've decided to fix the issues listed above. From now on you should now get back timestamps that include a timezone and are formatted in a manner useful for an international audience.

Using the example above, you'll now see this:

example_address@nowhere.com
75.149.211.42
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;)
2011-09-14T19:26:00.00+00:00

That's much better! It's clear that this timestamp is in UTC, and it's in a much more internationally friendly Year-Month-Day format.