41
edits
Difference between revisions of "Myths"
Jump to navigation
Jump to search
→Myth Two: The baseline is minimal, therefore XMPP is useless.
| Line 29: | Line 29: | ||
The fact: XMPP is designed to be extensible, and many extensions have very broad deployment. | The fact: XMPP is designed to be extensible, and many extensions have very broad deployment. | ||
"It's a feature, not a bug" is the obvious thing to say here. XMPP's core, RFC 6120, doesn't even include the "classic" IM features, really; those are present in | "It's a feature, not a bug" is the obvious thing to say here. XMPP's core, RFC 6120, doesn't even include the "classic" IM features, really; those are present in its companion specification, RFC 6121. As a protocol that's nearly fifteen years old, had the core been constantly redesigned to add new capabilities as new mandatory, baked-in features, lots of existing servers would have been redeclared as broken. | ||
Instead, what we have is a pretty large number of extensions to a clean core. This core defines, amongst other things, how to extend the core properties of the connection - but in fact the community designed an end-to-end extension system early on. | Instead, what we have is a pretty large number of extensions to a clean core. This core defines, amongst other things, how to extend the core properties of the connection - but in fact the community designed an end-to-end extension system early on. | ||
While you can still connect a client that supports no extensions at all to a server and have it work, nearly every client supports a wide range of extensions suited to its purpose, and every server supports several. | While you can still connect a client that supports no extensions at all to a server and have it work, nearly every client supports a wide range of extensions suited to its purpose, and every server supports several. | ||
== Myth Three: It's too bandwidth-inefficient for mobile. == | == Myth Three: It's too bandwidth-inefficient for mobile. == | ||