Jabber (English []: "„(therefore it) plappern "“) a free alternative is to prop. guessing eras Instant Messaging networks.

Within this range usual functions are supported such as transmission of news, conferences with several users, announcements of on-line status, file transmissions and many further services. Substantial characteristics of Jabber are the distributed, decentralized structure and the use from XML minutes to data exchange. In addition Jabber permits over as mentioned "„transport "“communication with users, those in prop. guessing eras to networks as ICQ or Yahoo! are announced.

The Jabber project was started at the beginning of of 1998 by Jeremie Miller. The first publicly released larger version appeared in May 2000.

Main part of the project is Jabber minutes. Also were realized: jabberd, a server software, with which Jabber Clients can connect themselves, over to chatten. So for example a private Jabber network behind a Firewall can be developed, or one can take part in the world-wide Jabber network.

The network architecture reminds thereby of from E-Mail: There are several servers of different offerers. On one of it the user furnishes itself an account. Messages then by the Client of the user to the server are conveyed, with which he registered himself, then send this server the message to the server of the receiver from there out them then finally to the Client of the receiver are, continued to transfer. Thereby it is insignificant whether both servers belong to the same offerer or not.

Googles of new VoIP and Instant Messaging service named Google talc are based on Jabber minutes.

First steps with the use of Jabber

The following is essential, in order to be able to use Jabber:

• Download of an Jabber able Clienten
• Installation and start of the Clients
• Put on a new Jabber account on a so-called Public server with the help of the Clients, which is usually free, and directly from the Client happened can. An exception is of it among other things Google.
• Log in and with Chatten in the Jabber network begin

Identities

The Jabber Identifier (JID) is the clear identification, with which each Jabber user is identified. The JID looks thereby usually like a E-Mail address, e.g.: myName@myJabberServer.com. The first part of the address is the node, which the user name indicates. A valid JID does not have to contain inevitably the node, behind JIDs without node hides itself however usually of programs. From node by "„@ "“separately, follows in the rear part the Domain, which determines the Jabber server, on which the JID is registered.

As the further information optionally resources can be attached (e.g.: username@ domain.com/zuhause). This indicates additional information, then for example an indication is possible of where one straight logged in is. With the help of this resources the server can meet a distinction, so that a user with the same JID from several computers can be logged in. With arriving messages on the basis a priority value one specifies, at which Client the message is delivered, if the exact goal is not already certain by resources. This priority value is specified by the user of the JID into the Clients, whereby larger numbers before smaller numbers have priority. The valid range goes from -128 to +127.

Conferences

Jabber supports conferences with several users, in addition the following minutes in the indicated order were developed:

• Groupchat
• Conference (only temporary in use)
• Multi-user Chat (MUC) e.g.: wikipedia@conference.jabber.org

Minutes preferred by many users are the current MUC. It is usable an extension of Groupchat minutes and thus even with older Clients, which support only Groupchat. The new MUC feature (for example role allocation for users within the Chats, password-protected or invisible areas) cannot be used then however.

Security

When using Jabber the connection is made between two Clients never directly, but always by at least one Jabber server. If the two Clients at two different servers are announced, thus the data communication takes place from the first Client to the first server, from this to the second server and from there to the goal Client.

Security makes Jabber possible here by coding the data links: Communication between the Jabber Client on user side and the Jabber server can be coded by SSL/TLS. The connection between Jabber servers can run off likewise coded, however this is not always the case. Since nothing is stated over the connection of the Chat partner to its server, this desired security nevertheless only partly offers. In addition it is possible for each server operator to read the messages sent away over it.

Remedy creates the use of an additional coding for the connection between the two Jabber users. The most common possibility represents here open PGP (END ton END coding).

Transport

A special concept of Jabber is that of transport. Hereby it is possible, other (in the Jabber jargon Legacy services ) networks mentioned such as AIM, ICQ, Yahoo! To use, Gadu Gadu or IRC and interact with their users. Also to MSN that is possible, for legal reasons switches off however many administrators this transport. Differently than with multi-logging programs, like Trillian (Instant of measuringclose), Miranda IN or Kopete, functions the connection to foreign nets with Jabber not by the fact that necessary minutes on Clientseite are supported. Instead everything that for communication with other networks is necessary, can do by which Jabber servers is supported. The servers transport thereby the messages between the networks, without the two users involved must take for this special precautions.

The following example is to illustrate the expiration between users J, which use a Jabber Client, and user I, which is registered with ICQ: User J hands first its ICQ dates of registration to the Jabber server over in the form of ICQ number and password. Thereupon the Jabber server logs in on behalf of J with ICQ and behaves for the ICQ network like a normal ICQ Client. It continues to transport on the one hand all messages of I (in the ICQ network) to the Jabber Client of J and leads on the other hand in the other direction all messages of J at Ith user I receives from this expiration nothing, for it looks it, as if it would interact with another ICQ user. In the contact list (with Jabber "“Roster"” mentioned) of J I is represented as "“more normally"” a Jabber user, although he is connected with the ICQ network actually not with the Jabber, but.

Advantage of this concept is that updates do not have to be distributed by new Clientversionen. Instead only the server software is updated, and all Clients profits directly from the changes.

Each user of Jabber can with one transport register itself, by indicating existing log in information for this service, and can then with users of these services communicate, as if these would be also Jabber users. Therefore each Clientprogramm, which supports the full range of Jabber minutes, without further change can be used for communication with all large prop. guessing eras Instant Messaging networks.

Although Jabber minutes do not give restrictions concerning the conversion of functions of foreign networks, current transport only basis functionalities (sending and receiving from message, visibilities) support. Datentransfers and are not over transport thus at present possible.

Transport of many users due to unsatisfactory reliability and stability as well as the high server-lateral load only as are regarded. They see the sense of the use above all therein, in a transition period the past contacts, which use still networks to migrate to Jabber. Justified of many users also continous use is regarded nevertheless as, since not all contacts have interest in a migration to Jabber.

An alternative to the use of transport is the use of Multi minutes Instant Messengern.

Standardisation and Foundation

Jabber minutes were adopted of the IETF at the beginning of of 2004 with some changes as Internet standard under the designation XMPP (Extensible Messaging and Presence Protocol).

The Jabber software Foundation is responsible for the standardisation on XMPP develop-developing that minutes, the so-called Jabber Enhancement Proposals. Structurally are the JSF into a board, a Council and the Membership divided.

Executive Director:

• Peter Saint Andre

Board 2005:

• Tonuses Bamonti
• Ryan Eatmon
• Ulrich Staudinger

Jingle extension

On 15 December 2005 Jabber software Foundation Publishes open VoIP and Multimedia Protocols. jabber.org, 15.12.2005 communicated the Jabber donation the extension Jingle, which extended the Jabber minutes by peer ton peer abilities. The Jingle extension is thereby an open version the Google talc extension to Jabber and by Google with is supported.

The published specifications divide thereby into two ranges: Jingle Signalling describes the underlying functions, in order to develop and keep upright peer ton peer meeting between two Clients, also by NATs. Jingle audio describes an implementation based on it of VoIP functions. In addition among other things Jingle profiles for video, UDP as well as internal Asterisk minutes are specified.

Articles in category "Jabber"

We found here 1 articles.

Related Websites

We found here 4 related websites.

• Jabber Clients
  There are literally hundreds of Jabber clients, many of which are listed on this page. ... The following is a complete list of Jabber clients. ...


• Jabber Overview
  Jabber is best known as "the Linux of instant messaging" -- an open, secure, ... Under the hood, Jabber is a set of streaming XML protocols and technologies ...


• Jabber Protocols
  The Jabber/XMPP protocols have evolved through an open design process within the ... The base XML protocols developed by the Jabber community in 1999 were ...


• Jabber Software Foundation
  Not-for-profit organization that oversees the general development of XMPP and maintains the Jabber...