Hi,
I got several reports that QWaveClient does not interoperate well with
WaveSandBox. In fact, I reliably managed to blow up a wave on wavesandbox or
forced some "shiny" messages. It turned out that WaveSandBox was the source
of these errors (see end of this mail).
I hacked around the bugs and according to my testing you can now chat with
WaveSandBox users via QWaveClient.
One problem remains: When inserting a new thread (i.e. creating a blip with
additional indentation), the thread will not show up on wavesandbox. Closing
and opening the wave on sandbox solves the problem. It seems that something
is really broken there.
Second, sending a <contributor> tag will force a shiny message. Therefore
QWaveClient does not send it anymore (for now).
Third, updating the conv+root first and sending the blip later lets the wave
blow up (I think this bug is well known).
QWaveClient now adheres to this order of sending things.
Fourth, sending one delta for the blip and one delta for conv+root right
after this one (this is the CORRECT order), results in the blip being not
visible in wavesandbox. The operations of the two deltas need to be joined
and sent as a single delta. Then it will work as expected.
Finally, wavesandbox uses some strange annotations:
annotation_boundary {
end: "user/d/Wlir8vFX"
}
This stuff is used all over the place and it is not specified anywhere.
Thus, QWaveClient ignores it.
Cheers
Torben
PS: Aldon, thanks for offering your server for the tests.
--
You received this message because you are subscribed to the Google Groups "Wave
Protocol" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.
