Sametime Links architecture

---

The Sametime links architecture consists of these components:

Sametime Links client. The client consists of a combination of Java™ and JavaScript code that runs in a browser. The client is designed to be lightweight and uses HTTP protocol to communicate with the server. The tests used a robot that simulates a large number of clients. These simulated clients perform the same operations as regular clients: log in, log out, watch other user's status, and send instant messages.

Multiplexer (Sametime MUX). Sametime MUX concentrates I/O operations in one place and thereby simplifies and reduces server load. It passes information to the community hub server that redirects the information to the specific server application (SA) that handles the request. The Sametime Links client to MUX data transfer is HTTP-based, whereas the communication between the different server components is virtual channel based and uses the Sametime proprietary protocol.

Community hub (also referred to as the core server component or Sametime Community). The community hub routes the requests between the different server components. In the case of Sametime Links, messages are passed between the Sametime MUX and the Sametime Links SA through the community hub.

Sametime Links server application (Sametime Links SA). A Sametime Links SA acts as proxy for a Sametime Links client. This SA communicates on one side with the Sametime Links clients using their HTTP-based protocol and on the other side with other Sametime components using the proprietary Sametime protocol.

---