Services

The SpeedLink Service implementation, running on the GridServer Engine, corresponds to the SpeedLink client implementation. SpeedLink clients connect to the SpeedLink Service implementation. Like GridServer, SpeedLink operations have the following lifecycle:

1.

Your application client tells the SpeedLink client what application Service to use.

2.

The SpeedLink client passes that information to the SpeedLink Service implementation.

3.

The SpeedLink Service implementation manages the application Service.

Consequently, application Service code need not change to run as a SpeedLink Service. If you deploy a Service with low-latency performance on your GridServer Broker, you can access it as a standard Service by having your client use ServiceFactory, or access it as a SpeedLink Service by using SpeedLinkServiceFactory. You can even access the same Service code as both standard and SpeedLink Service instances from within the same client process.

In contrast to GridServer Services, the SpeedLink Service itself manages the connection back to the SpeedLink client, receiving Service input and returning output, like a simplified version of the GridServer Engine's connection to a Broker. It also watches the ALLOCATION_TIME and IDLE_LINGER timers, ending the Engine's reservation when those total or idle timers expire, respectively.