If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

X-Weave-Timestamp milliseconds

VERIFIED FIXED

Status

Cloud Services
Server: Sync
VERIFIED FIXED
6 years ago
6 years ago

People

(Reporter: rnewman, Assigned: rfkelly)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa+][sync 2.0])

(Reporter)

Description

6 years ago
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.)
Whiteboard: [qa+]
Assignee: telliott → rkelly
Whiteboard: [qa+] → [qa+][sync 2.0]
It'll be centiseconds (hundredths), and it'll be the format in 2.0. Not sure we need X-Weave-Time as well.
Correction. It will be in integer milliseconds for everything
(Assignee)

Comment 3

6 years ago
This has now been committed for sync2.0, timestamps are integer milliseconds throughout
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Already done and in code.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.