Peer to Peer Services
Universal Messaging provides a rich set of APIs that provide developers with the ability to create Peer to Peer (P2P) applications. We call these Peer to Peer applications Services. This guide will demonstrate how Universal Messaging Peer to Peer Services work, and provides examples code snippets for all relevant concepts.
P2P Service Components
There are two parts to a Peer to Peer Service in Universal Messaging: a Server Service and a Client, in Flex only the client portion is available. To see more information about the Server service see either the Java , C# or C++.
A Universal Messaging Peer to Peer Client is a process that connects to a Universal Messaging Realm, obtains a reference to a Server Service and begins communicating with it.
When a Client connects to the Server Service, all communication between the Client and server service takes place through the Universal Messaging Realm, using Universal Messaging's standard communication protocols.
P2P Service Types
There are two types of Universal Messaging Peer to Peer Services, Flex only supports Event Based Services:
Universal Messaging Peer to Peer Event-based Services communicate via events which are published by the Event-based Client, and received and responded to by the Event-based Server Service.
The following examples give methods needed to implement a client to work with Java, C# or C++ Server Service:
For more information on Universal Messaging Peer to Peer Services please see the API documentation.