Re:Google Wave Drips With Ambition. A New Communication Plat...
by zaatar on Thursday May 28, 2009 @12:32PM
(#630494)
It is an open protocol: http://www.waveprotocol.org/
[ Parent
| on HN ]
Re:Google Wave Drips With Ambition. A New Communication Plat...
by est on Thursday May 28, 2009 @01:42PM
(#630665)
it's xml based http://www.waveprotocol.org/draft-protocol-spec
looks like XMPP to me
I really hate XML
Re:Google Wave Drips With Ambition. A New Communication Plat...
by jonke on Thursday May 28, 2009 @02:13PM
(#630727)
Even if I agree somewhat with your feelings about xml, I think I prefer something like xml over (a sample) of:
RFC 1939 POP3 protocol Updated by RFC 2449
RFC 2449 POP3 Extension Mechanism
RFC 822 STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES Obsoleted by RFC 2822
RFC 2822 Internet Message Format
RFC 2045 MIME Part One: Format of Internet Message Bodies Updated by RFC 2231
RFC 2046 MIME Part Two: Media Types
RFC 2047 MIME Part Three: Message Header Extensions for Non-ASCII Text Updated by RFC 2231
RFC 2183 The Content-Disposition Header Field Updated by RFC 2231
RFC 2231 MIME Parameter Value and Encoded Word Extensions: Character Sets,...
RFC 2387 The MIME Multipart/Related Content-type
RFC 3462 The MIME Multipart/Report Content-type
RFC 2111 Content-ID and Message-ID Uniform Resource Locators
RFC 2632 S/MIME Version 3 Certificate Handling
RFC 2633 S/MIME Version 3 Message Specification
RFC 2821 Simple Mail Transfer Protocol
Re:Google Wave Drips With Ambition. A New Communication Plat...
by mcav on Thursday May 28, 2009 @02:18PM
(#630733)
MIME isn't complicated, nor does it look any more jumbled than XMPP.
Re:Google Wave Drips With Ambition. A New Communication Plat...
by rcoder on Thursday May 28, 2009 @05:08PM
(#631024)
Yeah, it looks a lot like XMPP to me, too:
"The Google Wave Federation Protocol is an open extension to XMPP core [RFC3920] protocol..."
(From the first paragraph of the draft spec.)Whatever your feelings about XMPP, I challenge you to point to a standardized, interoperable protocol that you think would be a better fit. It may not be ideal, but it's extensible, already supported by a large number of clients and servers, and doesn't require starting from scratch when building interoperable software.
Re:Google Wave Drips With Ambition. A New Communication Plat...
by mcav on Thursday May 28, 2009 @02:04PM
(#630705)
It's an XMPP extension.
Re:Google Wave Drips With Ambition. A New Communication Plat...
by mattmcknight on Thursday May 28, 2009 @10:51PM
(#631437)
I think there is room for something like AMQP. Most people use libraries to process XMPP anyway, so a binary format wouldn't be a huge change (except, perhaps, in performance).
Re:Google Wave Drips With Ambition. A New Communication Plat...
by vidarh on Friday May 29, 2009 @05:47PM
(#632880)
After starting to read the AMQP spec I wanted to claw my eyes out.
Re:Google Wave Drips With Ambition. A New Communication Plat...
by dualogy on Thursday May 28, 2009 @04:18PM
(#630958)
Yeah, me too, but writing a bi-directional wrapper for JSON or the even better future thing might be non-trivial -- unless the protocol gets ugly and uglier.
Re:Google Wave Drips With Ambition. A New Communication Plat...
by known on Thursday May 28, 2009 @11:33PM
(#631475)
XML is not suitable for Mobile Platform.
Re:Google Wave Drips With Ambition. A New Communication Plat...
by sketerpot on Friday May 29, 2009 @12:35PM
(#632309)
Why not? It's simple enough, and there exist small, fast XML parsers with low memory footprints.
Re:Google Wave Drips With Ambition. A New Communication Plat...
by known on Saturday May 30, 2009 @04:22AM
(#633417)
I'll enumerate the implications and conclusions:
1. XMPP is verbose.
2. XMPP is inefficient for mobile networking.
3. A proprietary binary protocol would be more efficient for mobile devices.
4. The former Android xmppService API will diverge away from XMPP.
http://www.deepdarc.com/2008/02/14/mobile-xmpp/