Given by TangoInteractive Team at Tango Tutorial San Diego MRA on June 26 27 98 Datemod;June 18 98. Foils prepared
Outside Index
Summary of Material
TANGO Functionality |
TANGO Current Capabilities |
TANGO Versions |
TANGO Components |
TANGO Application Protocols |
TANGO Session Management |
Outside Index Summary of Material
Prepared by Marek Podgorny and Tango Team |
Presented by Geoffrey Fox |
NPAC, Syracuse University |
MRA Meeting San Diego June 26-27 1998 |
TANGO Functionality |
TANGO Current Capabilities |
TANGO Versions |
TANGO Components |
TANGO Application Protocols |
TANGO Session Management |
It lets applications controlled by your browser to talk to Web application run by other people
|
TANGO turns a web browser into a communication program
|
Technically, it is a multiparty, multi-session, multiplatform, multimedia collaboratory system |
It is also a software integration framework
|
N: Netscape Browser |
LD: Local Daemon |
CA: Control Application |
AP: Applet |
LA: Local Application |
CS: Central Server |
DB: Back-end Database |
HTTP: Web server |
It must be competitive with best available collaborative tools and so its multi-language interface allows us to interface to other systems with Tango supplying Integrated Session Control
|
Basic model is that of a room which is a group of people getting together for a class
|
Each room supports a collection of shared objects chosen by teacher/students/administrator |
TANGO supports over 40 applications |
Core Collaboration Capabilities
|
95 |
Office and Authoring Tools
|
General Virtual University Applications
|
Special Virtual University Applications
|
Chat |
Shared Browser |
Audio Control |
Tango Control App |
WebWisdom |
CONTROL |
Shared Planetary Motion Applet |
Shared Cross Product Educational Applet |
Shared Neural Net |
Have some fun with multi-player games
|
"Other" Applications
|
CONTROL |
Shared VRML 3D Visible Human |
Shared Browser Page |
Chat |
Public version: version 1.0 beta 4 |
July 7 1998: version 1.0 Deployed
|
Expected Sept `98: TANGO 1.1
|
Over next year much improved distance education and collaborative research support e.g. shared visualization
|
TANGO 1.x requires browser plug-in |
Compatible with Netscape Navigator 3.0 and 3.01
|
Compatible with Netscape Communicator 4.x
|
The system is available now from http://www.npac.syr.edu/tango |
Supports all the same features as TANGO 1.0 beta4 |
Employs modified protocol between the plug-in and the collaboratory server
|
Version 1.0 requires re-installation of both server and client software |
Version 1.1 will support MS Internet Explorer 4.x |
Java application
|
100% maintenance free |
Industry-strength stability |
Platform-independent
|
Available for download from http://www.npac.syr.edu/tango |
Daemon provides a mechanism for TANGO components such as Java applets, central server, JavaScript scripts etc. to talk to each other. |
TANGO daemon has been implemented as a plug-in. |
Using LiveConnect mechanisms, each applet residing in the same page with the plug-in may obtain its handle. |
Message passing between plug-in and an applet is achieved by calling appropriate methods of each other |
Local Daemon's main tasks:
|
The daemon is implemented as a plug-in to Web browsers.
|
Central Server is the main communication element.
|
Java applets
|
Local Applications:
|
Control Application provides TANGO GUI
|
Since TANGO uses central server architecture, there are system scalability concerns.
|
For scaleability reasons, the real time multimedia streams are not sent via central server. |
Instead, we use a distributed architecture akin to the Insoft's OpenDVE |
The architecture supports multicast. |
Session control remains with the TANGO session manager. |
TANGO VTC supports stream recording, storage, and retrieval |
A blueprint for a truly successful collaboratory system does not exist. Hence:
|
The essence of each collaboratory function must be defined by application and by application only |
TANGO does not define any application protocols |
Basic API requires application developer to implement application protocol conversion to byte streams |
More advanced APIs handle more complex situations
|
A session is a group of application instances currently working together in the collaborative mode.
|
Master status is dynamically transferable. Floor control allows for both master-master and master-slave relationship |
TANGO does not restrict the number of concurrent sessions. There may be multiple independent sessions of applications of the same type. |
Messages from one application compatible with application of another type will be distributed transparently. |
Currently supported operations:
|
CA implements "intelligent interface" |
General questions
|
Architecture, client setup
|
Server
|
Applications
|
http://www.npac.syr.edu/tango |
FOR MORE INFO... |