> XMPP > Advantages: > XML Based (almost anyone can parse it) > Already in use in other Wave–related protocols > reduces the quantity of things a prospective wave developer has to > learn > reduces the number of dependencies (at least for wave servers, the > clients don’t care about the part that already uses xmpp) > great for mini–servers, such as one might tie into an existing web > application to integrate waves as a data model for discussion > (forums, blogs with comments, so on and so forth) or as a new data > model for anything else real–time and with multiple contributors > (code editors, other crap?)
Add to that list: Potential ability to transit presence information (or other meta-XMPP state information) up to the GUI layer. This, IMHO, is the big win; since we're sitting on top of an XMPP server, it makes sense (from my point of view) to put ourselves in a position to leverage all of its capabilities (in ways that are not currently obvious or even necessarily available). When we get to that point (the "we" here is not the Google Wave team, it's an otherwise unnamed group working to extend XMPP for rich presence data), we (Wave developers) would need a client that speaks to the Wave server in its native tongue, as well as being able to craft XMPP that can be interpreted by the underlying XMPP box (communication passing through the Wave server enroute). Better that the two are compatible so that the client only needs to have one protocol internally... -- Jorj
PGP.sig
Description: This is a digitally signed message part
