Difference between revisions of "Time Epochs"
| Line 14: | Line 14: | ||
|- | |- | ||
| <code>01 Jan 1970</code> | | <code>01 Jan 1970</code> | ||
| − | | [[#Unix_Time|Unix Time]] | + | | [[#Unix_Time|Unix Time]]<br />[[#Firefox|Firefox]] |
|- | |- | ||
| <code>01 Jan 2001</code> | | <code>01 Jan 2001</code> | ||
| Line 26: | Line 26: | ||
=Chrome= | =Chrome= | ||
Chrome stores the time as a 64-bit integer representing the number of microseconds since 01 Jan 1601. | Chrome stores the time as a 64-bit integer representing the number of microseconds since 01 Jan 1601. | ||
| + | |||
| + | =Firefox= | ||
| + | Firefox ([https://firefox-source-docs.mozilla.org/nspr/reference/prtime.html PRTime]) stores the time as a 64-bit integer representing the number of microseconds since 01 Jan 1970. | ||
=Unix Time= | =Unix Time= | ||
Revision as of 11:14, 8 June 2024
Here's some of the time formats that Truxton can handle. Wikipedia has a better list. The Truxton software uses FILETIME for all time calculations.
| Epoch | Type |
|---|---|
01 Jan 1601
|
Windows FILETIME Chrome |
30 Dec 1899
|
Windows COM |
01 Jan 1970
|
Unix Time Firefox |
01 Jan 2001
|
Apple |
Apple Cocoa Core
Cocoa Core (aka NSDate) is the number of seconds (32-bit value) since 01 Jan 2001. The 64-bit version is the number of nanoseconds since 01 Jan 2001.
Chrome
Chrome stores the time as a 64-bit integer representing the number of microseconds since 01 Jan 1601.
Firefox
Firefox (PRTime) stores the time as a 64-bit integer representing the number of microseconds since 01 Jan 1970.
Unix Time
This is a 32-bit integer holding the number of seconds since 01 Jan 1970. The 64-bit integer version holds the number of milliseconds since 01 Jan 1970.
Windows COM
Windows [Component_Object_Model COM] stores date time in a double (floating point) number representing the number of days since 30 Dec 1899.
Windows FILETIME
A 64-bit integer containing the number of 100-nanosecond clock ticks since 01 Jan 1601.
