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.)
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
This has now been committed for sync2.0, timestamps are integer milliseconds throughout
Status: NEW → RESOLVED
Last Resolved: 7 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.