TimeStamp of new blips appear as "December 31st 1969" until the client is refreshed

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Load a wave in a WiaB client
2. Wait for someone to post a blip, or post one yourself using a second account
3. Check the timestamp on the blip

What is the expected output? What do you see instead?
I expect that the date it is created should be shown.
I see "December 31st 1969"

Original issue reported on code.google.com by nat.abbo...@wavewatchers.org on 11 Dec 2010 at 9:42

[GoogleCodeExporter]

This sounds similar to Issue 135 and there are still some metadata fixes needed 
in the c/s protocol.

Original comment by ano...@google.com on 13 Dec 2010 at 12:04

• Changed state: Accepted

[GoogleCodeExporter]

It seems the issue is fixed...

Original comment by vega113 on 21 Jan 2011 at 11:16

[GoogleCodeExporter]

Not fixed. To reproduce:
- Log in to two different browsers and open the same wave
- In one browser, make a new blip
- In the other browser, it appears with a 1970 timestamp

The timestamp is corrected when the wave is re-opened. The cause is that the 
existing c/s protocol has no timestamp for document updates (but does for 
snapshots).

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

• Changed title: TimeStamp of new blips appear as "December 31st 1969" until the client is refreshed

[GoogleCodeExporter]

Issue 137 has been merged into this issue.

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