I'm gonna also vote for the C/S protocol to use XMPP. I've successfully implemented XMPP over BOSH and it rocks. In fact, I've built quite a bit of XEP-60 (the XMPP pubsub protocol - used by Wave) in JavaScript for use in what you might think of as 'browser-based client/server apps', so I know it can be done.
As far as the old JSON vs. XML argument - I've run the numbers and it just doesn't add up. Once you gzip the XML, it can actually be smaller than the JSON - it doesn't seem possible, but there it is. In a way, JSON is a bit of an optical illusion - it only looks smaller to the humans. The ProcessOne guys rock and they've already built some of this, showing off a Wave client that is an extended version of an XMPP client written in Tcl/Tk. If anyone from ProcessOne is out there, please join in the conversation here. Cheers, - Bill On Oct 1, 7:03 pm, elliottcable <[email protected]> wrote: > Oh, worth noting: I cross–posted a wave on this subject; if you’re in > the preview (not the Sandbox!) click: > > https://wave.google.com/wave/#restored:wave:googlewave.com!w%2BsyQLkEm6V --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
