That is very strange. It almost looks like websocket is sending binary data instead of text?
I don't know much about Chromium vs. Chrome, but I will look into it tomorrow morning. It might be a WebSocket binary framing issue. J.D. On Thu, May 27, 2010 at 1:00 AM, Anthony Baxter <[email protected]> wrote: > Something's very badly not right there. JD, any ideas? Is it possible > that Chrome revved the version of Websockets that they support? > > > On Thu, May 27, 2010 at 17:58, James Purser <[email protected]> wrote: >> INFO: received JSON message ^Z???} >> >> -- >> 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. >> > > > > -- > Anthony Baxter, [email protected] > > -- > 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. > > -- 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.
