Tango architecture - a programmer's perspective

Two major entities in Tango are a user and a session. Each user has access to a session manager, a.k.a. control application. Session manager allows users to run collaborative applications. Every running application belongs to a session, and users joining the application become participants of the application session.

When an application is started it can either join existing session or create a new one. If it joins an existing session, the user is added to the group of participants of the session and becomes a slave in this session. If the application creates a new session, the user becomes the first participant of a new session and the session master. There is always one master per session. System information such as users, sessions, session participants, and session master is available from the Tango API.

Tango's communication backbone ensures that messages between all applications in a session are properly routed. Using Tango API, messages can be broadcasted or sent to selected participants addressable with their names. However, it is application's responsibility to implement functionality and use appropriate communication protocol that renders that application collaborative.

Implementing collaborative applications usually consists of:

The attached documentation explains in detail how to create collaborative Internet application in any of the following programming languages: Java, Javascript, C, C++, and LISP.


Last modified: Wed Oct 13 18:58:40 EDT 1999
Address questions related to Tango API to support@webwisdom.com.