Languages and IO

One of the primary requirements for the shim is that it shield the downstream from the binary IB tws protocol by converting that format to a convenient textual form. There are then at least two protocol languages that the shim must speak, binary for upstream and text for downstream.

Once given a textual language with which to express events, they must be copied somewhere to be of use, and so there are several channels to which the shim can echo events, though one in particular is always primary, currently either a text file in the current directory, or else the system logger.

The format of requests and messages is described in § 6.1; that of commands and the output stream in § 4.3; and the names and other attributes of the output channels to which the output stream can be directed, in § 6.2.



Subsections

Bill Pippin 2010-01-14