Specifications

COM+ reference

Gallagher & Robertson Glink: API reference manual 5

’Thin-client’ (GlinkApi.GlinkApi)

The thin-client GlinkApi COM+ component included in Glink is a multi-

threaded multi-object out-of-process server. This means that each time a new

GlinkApi object is created it is created within the same GLINKAPI.EXE

instance and only requires memory allocation for the new object. Each new

instance is always invisible and completely independent from any other

instances. It is ideal for workstation client applications and perfect for server

applications due to its small footprint size, its multi-threaded and multi-object

architecture.

The GLINKAPI.EXE server is started automatically on demand by the Windows

system and is completely invisible to the user. To help developers, it can also be

started upfront with the /J command line option to enable a debug window used

for trace output.

The thin-client GlinkApi class name is GlinkApi.GlinkApi and is included

in both the Glink Professional edition and Glink Enterprise edition.

Before you can use the GlinkApi component, the GlinkApi server needs to

the GlinkApi COM+ components when it is installed but you can explicitly

glinkapi.exe /regserver

glinkapi.exe /unregserver

When the above commands are used, the GlinkApi server will automatically exit

after registering the GlinkApi class.

Once registered, you can immediately start using the GlinkApi.GlinkApi

class from other applications, or from visual development tools that can import

COM+ components.

The thin-client GlinkApi COM+ component can execute within the MTS

(Microsoft Transaction Server) architecture as an out-of-process server, making

Glink the perfect host access component for your E-business applications on the

Microsoft platform.

The GlinkApi component also includes the standard SESSION and

APPLICATION objects available in Active Server Pages (ASP) within

Microsoft's IIS.