Specifications

COM+ reference

Glink: API reference manual Gallagher & Robertson

GlinkApi class

Class GlinkApi

GlinkApi

class GlinkApi

This is the main class for the API interface to Glink. The class is contained in the

glink.jar file delivered. The Java class path must be adjusted so this jar file can

be found.

To start Glink from an application, create a GlinkApi object and supply the user

name, password and session name with the userName, userPassword and

sessionName methods. Then call the start method to launch Glink.

Restricted mode

When Glink is running as a J2EE connector, the J2EE application server will

place the API in Restricted mode before passing it to client applications. When

in Restricted mode, some methods will silently do nothing. These methods are

marked as Restricted in this documentation.

Message mode and character sets

In message mode, Glink bypasses the emulation and sends and receives data

directly between client and host. In emulation mode, clients always work in

ASCII/UNICODE regardless of the host character set, as data is always assumed

to be textual.

In message mode, binary data transmission is possible. This is implemented by

two sets of message mode functions. One set works much like emulation mode

in that data is always in ASCII/UNICODE as seen from the client, regardless of

the host native character set. The other set allows transmission of raw data

buffers in the host native character set. The difference between these two sets is

that the former operates on String data, the latter operates on byte arrays. See the

relevant messageModeXXX() methods below for details

Java only