The session services APIs provide a general scrolling I/O interface. They can be used to build a standard input-line scrolling interface or an interface that has an output-only scroll area (called a scroller) in a window. Sessions are special cases of windows as supported by the window services. A session is defined using a session, a window, and a low-level environment description. The window and low-level environment descriptions are the same as those used to define a window directly with the window services APIs. The session description defines the structure of the session. The structure includes the coordinates of the scrolling portion, the length of the input line, the amount to roll by, and so on. A session is implemented as a window, where the window user data pointer describes the session itself. Thus, a session can be manipulated through the window and low-level interfaces by passing the session handler or through the session interfaces. This implementation is similar to the concept of inheritance in object-oriented programming languages.
Sessions are similar in concept to subfiles and can be used for any application that requires a scrolling line interface. The session services APIs are divided into the following functional groups:
For additional information, select one of the following:
| Top | Dynamic Screen Manager APIs | APIs by category |