HI, I think that having standarised XMPP c/s protocol is good think.
But even this will not stop anyone (including Google) to write their own c/s protocols (becuase ie. they think something like json is faster/simpler/smaller for JavaScript) for particular (in. Google Wave web client) reason. But as I said, there should already be XMPP protocol for it, and only after it think about optimalisations. If we will not work about it, there will some ad-hoc standards, cooperativly not compatible and with possibly many own problems. The best we can do currently is probably to base c/s on (subset? of) federation protocol, so it will be simpler to parse, generate & forward data, both in server and client. Regards, Witek -- 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.
