Instant Messaging / Build your own Peer-to-Peer Application! Services Provided by the API The mCommunicator Peer-to-Peer Toolkit provides the following services: Naming Services: Each applicaion running the mCommunicator API is provided an unique name, and all data exchange is carried out with this named entity, regardless of where in the DNS space the entity exists. Routing Services: The Toolkit ensures that messages are transactionally delivered between two nodes. The messaging is primarily peer-to-peer and uses the server to provide routing services incase NAT's and Firewalls make peer-to-peer message delivery impossible. Presence Services: The Toolkit allows a node to quesry presence information about any node and determine its status. Directory Services: Each node may register information about itself in the central directories and this is used for status information about nodes. (Example use is for maintaing file lists in file-sharing networks) Message Caching: At the senders discretion, messages that can not be delivered to the end node immidiately can be cached unit the recipient is online again. This service is provided by the server system. Easy to add Client Side Controls The Client side of the API is available as ActiveX Controls or as Java Beans so that the developer may plug them in to his applicaion with ease. Platform Independent Server Side The server component of this architecure provides some of the services, inlcuding presence management, and fall-back routing. The server is a lightweight applicaion that is by design both platform adn database independant. Demonstration The mCommunicator instant messaging network has been bulit on top of this API. More Information For more information and architectural documents please contact, Esther DSouza, (email: p2p-at-megaeservices.com) or at +91 (22) 2023015		Instant Messaging Introduction Coporate Messaging Peer-to-Peer API How can you practically deploy Peer-to-Peer applications?