Jabber For Messaging

Jabber-It is a messaging protocol which has its prime features-
1. Presence based-providing advantage of Real-Time messaging
2. Open source
3. XML-Based making it future proof
4. Distributed client server architecture(hub and spoke model)-making clients a minimal entity
5. Multiple client Access-user can have multiple clients logged in at the same time each known as “Resource”

Keywords related to Jabber-:
Users-User is what can be called as client, but each user can have multiple clients called “Resource”.
Domain- Domain is address of server or server name, in jabber each Domain can connect to other domains that are present in the network, and talk to clients that are connected to that Domain, (star and star are connected to form network.
JabberID-It is a unique identification to the server of that user .Each JabberID can have multiple resources. Each ID has a standard structure i.e. “:user@domain/resource”
High level entities(Muse API)-:
Jabber Context-It is a container for the information about the user which is used as login information.
Jabber Session-each jabber context is logged in with a jabber session, which is somewhat like a pointer to the server.
All the interactions made with server are performed by each session that we register in server, and server in turn provides services based on request.
Roster-It is a technical name for “buddy list “ that you see in messenger, typically server displays the Presence information of certified users to client.

Advantages-
1. Open source
2. Good biosphere
3. Tested for enterprise applications

Muse API for jabber/XMPP:
It is a java implementation of client programming with Jabber . Muse API is very easy to use and well documented.
Link to javadoc:http://www.echomine.org/muse/javadocs/Download page: http://www.echomine.org/confluence/display/MUSE/2.1+Download+Muse