TOC2 protocol
Encyclopedia
The TOC2 protocol is an updated version of the TOC protocol
TOC protocol
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...

, or "Talk to OSCAR" protocol. Its existence was never documented by AOL
AOL
AOL Inc. is an American global Internet services and media company. AOL is headquartered at 770 Broadway in New York. Founded in 1983 as Control Video Corporation, it has franchised its services to companies in several nations around the world or set up international versions of its services...

 and it is only used in a few AOL Instant Messenger
AOL Instant Messenger
AOL Instant Messenger is an instant messaging and presence computer program which uses the proprietary OSCAR instant messaging protocol and the TOC protocol to allow registered users to communicate in real time. It was released by AOL in May 1997...

 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
OSCAR protocol
OSCAR or Open System for CommunicAtion in Realtime is AOL's flagship instant messaging and presence information protocol. Currently, OSCAR is in use for AOL's two main instant messaging systems: ICQ and AIM....

, 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
Porting
In computer science, porting is the process of adapting software so that an executable program can be created for a computing environment that is different from the one for which it was originally designed...

 code from TOC to TOC2 is remarkably easy as well.

AOL's TOC Server

The following are servers and port information for OSCAR and TOC:
  • toc.oscar.aol.com:9898
  • aimexpress.oscar.aol.com:9898


Login (Authentication) Server:
  • login.oscar.aol.com:5190


As of 10 Sept. 2011, neither of the above-mentioned TOC servers allow inbound connections on the specified ports.

Changes from TOC

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 amount of ScreenNames 1 IP address can login (10)

External links

The following update to the original protocol documentation includes numerous additions and corrections, including a simplified way to calculate the username and password login code:

Implementations

The source of this article is wikipedia, the free encyclopedia.  The text of this article is licensed under the GFDL.
 
x
OK