• You can build plain html files that include Tango Tags that get processed by the Tango Server. These TML (Tango Markup Language) files can be very useful especially since they allow you to create static links between web pages while allowing you to maintain user variables.
• Tango files are now written in an XML format and can be created and maintained in any text Editor. At the same time you still have the familiar graphical editing environment to fall back on if you don't want to "get under the hood". This means that, among other things you can create template TAFs and then alter one or two items (say the Database connection) and have a working TAF. This concept can be extended to having Tango Applications that dynamically write other Tango Applications.
• Since Tango itself is written in XML you now have new tools for working with XML documents. For example, by simply changing the MIME type of the document you can write other XML standards such as WML (Wireless Markup Language) for use with special platforms.
• On top of this several standard tags and actions have been enhanced and new ones have been added. Two good examples of expansion are the Mail Action, which now supports file attachments, and the <@URL> tag which now supports 128-bit encryption. On the other hand you can now have new tags such as <@VISTORID> that let you track users, <@CLEARERROR> which allows you to "ignore" an error and continue processing. In such a case you could use new functions to write your own message into the Tango Log file.
• If expanded tags interests you, then how about the ability to write your own meta tags. This is done with a Tango Class File or TCFs. Imagine a tag that retrieved all of the items in a lookup table and created a drop menu for inclusion in your edit screens. All in a single tag! Or a meta-tag that did some huge calculation in a single step. If you like R:BASE UDF DLL's or Stored Procedures you have the general idea of why this is such a cool thing. One Tango developer actually built a set of TCF's that allows Tango to interpret and process Cold Fusion code.
• With the addition of TCF's and support for COM objects (imagine a COM object that could read and write the Windows Registry) Tango 2000 has all the advantages of Tango 3.6, such as rapid development and easy maintenance, plus an expanded and extendable framework in which to develop new applications.
• On top of all that (and more) Tango 2000 will run your Tango 3.6 and 3.5 applications without conversion. Simply install Tango 2000 and you are up and running. It's that simple! In case nobody heard us mention it, the Tango demonstrations at the Millennial Developers' Conference (the ones run off of the local web server) were run by Tango 2000... even though they were written in Tango 3.6!

How Does R:Tango Work?

1. A web browser such as Internet Explorer or Netscape Navigator makes a request using Hyper Text Transfer Protocol (HTTP).
2. A Web server such as Microsoft's Internet Information Service (IIS) or Netscape's Fastrack Server receives the request.
3. When the request is for a TAF (a Tango Application File) then Tango interprets the Uniform Request Locator or URL to determine which application is needed and where in the application you wish to go. This request to Tango is either handled via the Common Gateway Interface (CGI) or through a Plug-in designed to support one of several standards. ISAPI (used with IIS), NSAPI (used with Netscape), or Apache Modules with Apache.
4. The Tango Server processes the request and executes one or more application files. These files contain actions which, when assembled into a whole, will fulfill the users request
5. Tango hands any database requests to Oterro via ODBC (Open DataBase Connectivity)
6. Oterro handles the interaction with the R:BASE database and returns the results to Tango, again, via ODBC.
7. Results from the R:BASE database are processed by Tango Server using the Results HTML associated with each Tango Action. Tango Server performs column substitutions and data manipulation for each row and generates the final HTML for presentation.
8. The accumulated HTML from all Tango Actions are then compiled into a single HTML page that is returned to the Web Server.
9. The Web Server then returns this HTML to the origination Web Browser, thus fulfilling it's original request.

Minimum System Requirements

• A Pentium Level Processor with a minimum of 128 megabytes (MB) of application Random Access Memory.
• Microsoft Windows NT Server 4.0 with Service Pack 6 or higher.
• A CD-ROM Drive (for installation only).
• 40 to 50 MB of available hard disk space (More may be required for your databases).
• VGA Display Card (for installation / configuration only).
• A Web Server that supports the CGI Standard.
• The ISAPI Plug-in requires Microsoft IIS 3.0 or higher.
• The NSAPI Plug-in requires Netscape 2.0 or higher.
• The Apache Modules require Apache version 1.3.6 or 1.3.9 for Windows.

R:Tango License Summary

• Each R:Tango suite, comprised of R:BASE, Oterro and Tango Server, is licensed for use on a single NT Web Server only.
• The Tango Development Studio is licensed for use a single machine. This can be either the server or another workstation.