4 ms·
The impression I get from this summary is that Google built a really nice web app and then decided to call it a "protocol", but it's actually just a high-level
by seldo 17y ago
The impression I get from this summary is that Google built a really nice web app and then decided to call it a "protocol", but it's actually just a high-level description of their architecture -- you cannot use the "protocol" without creating something functionally identical to their architecture (compare to, say, email and FTP, where you can create a trivial client or a rich one on the same protocol).
- tlrobinson 17y agoThe Google Wave client could exist independent of at least the federation part of the Wave Protocol, if Google didn't care about interoperability with 3rd parties. That said, they're not stupid, of course, so they realized unless they make it open and bake in federation from the beginning they'll never get widespread adoption. Now if Wave does become popular, Google will be in a pretty good position. They invented the thing so they are experts in it, and have a big head start over everyone else with things like the Spelly and Rosy robots, and likely a more scalable infrastructure than the reference implementation they plan to open source. They'll also have a lot of control over the protocol. I'm not sure where I was going with that.