Document timestamps are missing from client/server protocol

latos / wave-protocol

Automatically exported from code.google.com/p/wave-protocol

0 stars 0 forks source link

Document timestamps are missing from client/server protocol #137

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Open new wave
2. Add new participant
3. Conduct conversation

What is the expected output? What do you see instead?
The timestamp should be accurate for each blip. However for the other 
participant it is always set to 1st January 1970

Original issue reported on code.google.com by JamesRPu...@gmail.com on 2 Nov 2010 at 12:05

Merged into: #180

GoogleCodeExporter commented 8 years ago

I very strongly suspect this has the same cause as Issue 135.

Original comment by ano...@google.com on 2 Nov 2010 at 12:14

Changed state: Duplicate

GoogleCodeExporter commented 8 years ago

Fair enough

Original comment by JamesRPu...@gmail.com on 2 Nov 2010 at 12:15

GoogleCodeExporter commented 8 years ago

I have a fix for Issue 135 but that still doesn't resolve this one as the 
timestamp data is missing from the protocol. This one requires changing the 
protocol (which I was about to do anyway).

Original comment by ano...@google.com on 6 Nov 2010 at 7:45

Changed title: Document timestamps are missing from client/server protocol
Changed state: Accepted

GoogleCodeExporter commented 8 years ago

Fixed?

Original comment by vega113 on 22 Jan 2011 at 9:25

GoogleCodeExporter commented 8 years ago

Original comment by ano...@google.com on 24 Jan 2011 at 1:19

Changed state: Duplicate