This article needs additional citations for verification. (July 2016)
The TOC protocol, or Talk to OSCAR protocol, was a protocol used by some third-party AOL Instant Messenger clients and several clients that AOL produced itself. Sometime near August 19, 2005, AOL discontinued support for the protocol and no longer uses it in any of the instant messaging clients it actively maintains, such as its Windows and Mac clients for the AOL Instant Messenger and ICQ systems. However, it once did produce several of its own TOC clients, including TiK and TAC which are written in Tcl/Tk, TNT which is written in Emacs Lisp, all of which are open source, and a Java client originally called TIC which later became the Quick Buddy web applet. AOL also provided the TOC protocol specification openly to developers in the hopes that they will use it instead of the proprietary OSCAR protocol they use themselves. In July 2012, AOL turned off the TOC2 servers and it is no longer possible to connect to AIM using this protocol.
TOC was an ASCII-based protocol, while OSCAR is a binary protocol. In addition, TOC contained fewer features than its OSCAR counterpart. OSCAR provides such functionality as buddy icons, file transfer, and advertising.
How it works
TOC acted as a wrapper for the OSCAR protocol. In the grand scheme of things, the TOC server was nothing but an OSCAR client that happened to listen on a socket, translating messages between the two protocols. Upon login, the TOC client specified an OSCAR login server (presumably either login.oscar.aol.com or login.icq.com) that the TOC server used on behalf of the client.
TOC used FLAP to encapsulate its messages just as OSCAR does, however, FLAP has been hacked in such a way that it can be implemented on the same port as an HTTP server. By default, the TOC server operated in HTTP mode, indistinguishable from a typical web server. If a connecting client, in place of an HTTP request, writes the string "FLAPON" followed by two CRLFs, TOC would switch gears and start reading FLAP messages. Upon getting a user's profile, the client was expected to re-connect to TOC and use it as an HTTP server, which would host the user's profile in HTML.
Once connected, two basic message formats for communications inside of FLAP existed. Client-to-server messages were sent in a format resembling a Unix-style command line: commands with whitespace-separated arguments, quoting and backslash escape sequences. Server-to-client messages were much simpler: they were sent as colon-separated ASCII strings, in a manner similar to many Unix config files. Thus, it was quite easy to write a client, as the incoming messages were very easy to parse, and outgoing commands were easy to generate.
This is in contrast to OSCAR, which due to the binary representation of data can be more difficult to understand.
The TOC2 protocol is an updated version of the TOC protocol, or "Talk to OSCAR" protocol. Its existence was never documented by AOL and it is only used in a few AOL Instant Messenger clients. Some clients are beginning to offer plugins for TOC2 in light of AOL's recent shutdown of their TOC servers. Like its predecessor, TOC2 is an ASCII protocol and lacks some features of OSCAR, but unlike TOC, TOC2 is known to support buddy icons and receiving file transfers (not sending). TOC2 operates in essentially the same way as TOC, as a wrapper for OSCAR. Porting code from TOC to TOC2 is remarkably easy as well.
Because of the similarities between TOC1.0 and TOC2.0, they are better defined by their differences, of which there are only a few:
- In TOC1.0, connecting with an empty buddy list would make it so that others are not able to see you online. This has been corrected in TOC2.0.
- In TOC1.0, there is a toc_add_deny command, but no toc_remove_deny. TOC2.0 corrects this as well.
- The sign on process is basically the same as TOC1.0, but with a few new parameters: version, a number, and a code created based on the username and password. The purpose of the number is unknown. The default is 160 and it seems to have no effect if changed.
- Permitting and denying have been revamped and are much easier and full-featured in TOC2.0. The commands toc2_add_permit, toc2_remove_permit, toc2_add_deny, and toc2_remove_deny are all present and accessible at any time.
- Buddy list commands have also been improved. Group management is easier with the toc2_new_group and toc2_del_group commands. Also, it is possible to add or remove more than one buddy at a time, and choose the groups they are in.
- A few syntax changes have also been made, and parameters have been added to some commands. The uses of these parameters are still undetermined.
- Aside from this the only changes from TOC are the fact that a '2' was added on most commands both CLIENT->SERVER and vice versa. E.g. IM_IN2, UPDATE_BUDDY2, etc.
- TOC2 also limits the number of ScreenNames that can log in from a single IP address (10).
- ^ "Possible end of AIM support [Update: Confirmed]". 27 July 2012.
- Detailed Specification[dead link]
- TOC1 Protocol specification[dead link]
- TOC2 Protocol specification Archived 2022-03-15 at the Wayback Machine
- History of AIM, OSCAR and TOC
- Py-TOC (python)
- Net::AIM (perl)
- PHPTocLib (php)
- Tik (Tcl/Tk)
- TNT (Emacs Lisp)
- TAC (Tcl, non-GUI)
- AOL Quick Buddy Applet (TIC) (Java Applet)
- naim (ncurses, non-GUI)
- miniaim (C++)
- SimpleAIM (Java)
- Fluent.Toc (C#)
- Raven::Aim (perl)
- Plugin for Miranda Instant Messenger
- PHPTocLib (PHP)
- BlueTOC (PHP)
- TerraIM (C++)
- TNT (Emacs Lisp)