|
|||||||
|
|
|
|||||
|
|
|||||||
Jabber |
|
Jabber: 'open source XML-based instant messaging.' "Essentially, Jabber defines an abstraction layer utilizing XML to encode the common essential data types. This abstraction layer is managed by an intelligent server which routes data between the client APIs and the backend services that translate data from remote networks or protocols. By using this compatible abstraction layer, Jabber can provide many aspects of an Instant Messaging (IM) and/or Presence service in a simplified and uniform way. At the core, Jabber is an API to provide instant messaging and presence functionality independent of data exchanged between entities. The primary use of Jabber is to give existing applications instant connectivity through messaging and presence features, contact list capabilities, and back-end services that transparently enrich the available functionality." "XML is used in Jabber to define the common basic data types: message and presence. Essentially, XML is the core enabling technology within the abstraction layer, providing a common language with which everything can communicate. XML allows for painless growth and expansion of the basic data types and almost infinite customization and extensibility anywhere within the data. Many solutions already exist for handling and parsing XML, and the XML Industry has invested significant time in understanding the technology and ensuring full internationalization. XML Namespaces are used within all Jabber XML to create strict boundaries of data ownership. The basic function of namespaces is to separate different vocabularies of XML elements that are structurally mixed together. By ensuring that Jabber's XML is namespace-aware, it allows any XML defined by anyone to be structurally mixed with any data element within the protocol. This feature is relied upon frequently within the protocol to separate the XML that is processed by different components." The Jabber Project: Statement on IETF Activity: "Jabber is an open development project and is commited to fully support any open real-time messaging protocols, including the IETF recommended protocol. When such protocol is available, users of Jabber software and services will automatically be allowed to communicate with users of the IETF protocol. As support for the IETF efforts grows, Jabber is aiming to create a leading open-source platform around its IETF support. The IMPP Working Group is currently entering the design phase for its protocol. Developers of the Jabber Project have been following the creation of the existing requirements draft closely, and expect to participate in the development of the protocol within the IMPP group. Based on the requirements draft, the protocol already used internally to Jabber is an existing possible candidate for the recommended protocol. As the IETF activity in designing the protocol continues, Jabber will be aligned as closely as possible to the discussions and requirements, and lobbied as a test platform for IMPP development efforts." References:
|