WindowsAzure/azure-sdk-for-node — pull request #81 by pofallon (2012-02-17 01:45:45+00:00)
Title: Handle milliseconds correctly in table storage date/time format

I experienced an issue where date/time values coming back from Azure were losing the milliseconds portion. Looking further I realized that atomhandler.js was calling ISO8061Date.format() to prepare values being sent to Azure, but not .parse() to interpret values coming back from Azure. Then looking at ISO8061Date.parse(), I realized that it was calling Date.UTC(), which returns a number (not a date value) so I updated it to return a date value per the comments in the method definition. I then updated the tests for ISO8061Date.parse() to test the actual creation of a Date object (not the UTC number, which both the test and .parse() were doing before, which is why it passed).

If I misinterpreted the purpose of the .parse() function, or how dates should be parsed in atomhandler, let me know.

Thank you!