68
edits
Difference between revisions of "Technology overview"
Jump to navigation
Jump to search
m
Added another link
m (Added link) |
m (Added another link) |
||
| Line 9: | Line 9: | ||
* Decentralized -- the architecture of the Jabber network is similar to email; as a result, anyone can run their own Jabber server, enabling individuals and organizations to take control of their IM experience. | * Decentralized -- the architecture of the Jabber network is similar to email; as a result, anyone can run their own Jabber server, enabling individuals and organizations to take control of their IM experience. | ||
* Secure -- any Jabber server may be isolated from the public Jabber network (e.g., on a company intranet), and robust security using SASL and TLS has been built into the core XMPP specifications. | * Secure -- any Jabber server may be isolated from the public Jabber network (e.g., on a company intranet), and robust security using SASL and TLS has been built into the core [http://www.xmpp.org/rfcs/ XMPP specifications]. | ||
* Extensible -- using the power of XML namespaces, anyone can build custom functionality on top of the core protocols; to maintain interoperability, common extensions are managed by the [http://www.xmpp.org/ XMPP Standards Foundation]. | * Extensible -- using the power of XML namespaces, anyone can build custom functionality on top of the core protocols; to maintain interoperability, common extensions are managed by the [http://www.xmpp.org/ XMPP Standards Foundation]. | ||