Closed
Bug 708956
Opened 14 years ago
Closed 14 years ago
X-Weave-Timestamp milliseconds
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Cloud Services Graveyard
Server: Sync
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rnewman, Assigned: rfkelly)
Details
(Whiteboard: [qa+][sync 2.0])
It sure would make life easier if we could get:
X-Weave-Time: ms
X-Weave-Timestamp: 1323393518040
rather than decimal seconds. Milliseconds since epoch. Parsing and validation is a bitch. Default to the old format, of course. Add to docs. Request header for time format. Yadda yadda.
(Same goes for info/collections, actually.)
|
||
Updated•14 years ago
|
Whiteboard: [qa+]
|
|
||
Updated•14 years ago
|
Assignee: telliott → rkelly
Whiteboard: [qa+] → [qa+][sync 2.0]
|
|
||
Comment 1•14 years ago
|
||
It'll be centiseconds (hundredths), and it'll be the format in 2.0. Not sure we need X-Weave-Time as well.
|
|
||
Comment 2•14 years ago
|
||
Correction. It will be in integer milliseconds for everything
|
Assignee | |
Comment 3•14 years ago
|
||
This has now been committed for sync2.0, timestamps are integer milliseconds throughout
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
|
||
Updated•3 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•