Google defends dropping chat federation with inaccurate comments

Re:Google defends dropping chat federation with inaccurate c... by josephg on Sunday May 26, 2013 @02:03AM (#5770214)

Google wave only used XMPP for federation. It was a nightmare to deploy and we never got it working reliably. Different jabber servers all had different quirks or implemented subsets of the XMPP extension spec.

The client-server protocol was simply JSON. XMPP was not involved. (Well, we translated protobuf messages to JSON, so it was ugly JSON, but still JSON).

[ Parent | on HN ]

Re:Google defends dropping chat federation with inaccurate c... by mh- on Sunday May 26, 2013 @03:44AM (#5770381)

(if you can't comment on this, no worries. thanks)

  we translated protobuf messages to JSON

just curious- is this the same 'protojson' I see exchanged in the current crop of APIs?

aside, any opinions on others choosing that as a standard way of communicating between internal services on disparate runtimes? (golang<->python, for example)

--

edit: offtopic, thanks for ShareJS.

[ Parent | on HN ]