[attachment=14093]
Abstract
The Extensible Messaging and Presence Protocol (XMPP) is an open technology for real-time communication, which powers a wide range of applications including instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data.
The technology pages provide more information about the various XMPP "building blocks". The core technology behind XMPP was invented by Jeremie Miller in 1998, refined in the Jabber open-source community in 1999 and 2000, and formalized by the IETF in 2002 and 2003, resulting in publication of the XMPP RFC in 2004.
Although the core technology is stable, the XMPP community continues to define various XMPP extensions through an open standards process run by the XMPP Standards Foundation. There is also an active community of open-source and commercial developers, who produce a wide variety of XMPP-based software.

XMPP is the Extensible Messaging and Presence Protocol, a set of open technologies for instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data.
1.3 Problem Definition
The level of protection depends on the correctness of the implementation by the Web browser and the server software and the actual cryptographic algorithms supported.
Also, it is unsecured when applied on publicly-available static content. This allows an attacker to have access to the plaintext (the publicly-available static content), and the encrypted text (the encrypted version of the static content).
Because Secure Sockets Layer operates below HTTP and has no knowledge of higher-level protocols, SSL servers can only strictly present one certificate for a particular IP/port combination.
The fact that XMPP is an open standard has led to its adoption by numerous software projects that cover a broad range of environ¬ments and users. This has helped improve the overall design of the protocol, as well as ensured a “best of breed” market of client applications and libraries that work with all XMPP servers.
To Overcome this Problem:
The objective of this project is to create an XMPP chat application for an organization capable of connecting to any XMPP server.
1. XMPP works over persistent connections
2. It stateful (becomes cheap)
3. Designed as an event stream protocol
4. Natively federated and asynchronous
-Globally and fire-and-forget information exchange. Participants in an asynchronous messaging system don't have to wait for a response from the recipient, because they can rely on the messaging infrastructure to ensure delivery. This is a vital ingredient in loosely coupled systems such as web services, because it allows participants to communicate reliably even if one of the parties is temporarily offline, busy, or unobtainable. Asynchronous messaging systems are also vastly more scalable than those that rely on direct connections, such as remote procedure calls.
5. Identity, security and presence are built in.
6. Jabber servers are built and deployed to do this stuff.
XMPP consists of XML streams that enable any two entities on the Internet to exchange messages, presence, and other structured information. Chat and presence are obvious candidates for real-time communication.
Unlike Stomp, XMPP messages are not sent in frames, but in XML streams that must be parsed carefully. The following lists of commands are some of the standard XMPP commands that we used built our application,
 Connect and disconnect
 Register
 Check roster
 Send messages
 Set status
 Communicate presence
This application is written in Java and MySql as database uses the XMPP library.