The Primary Client/Server Interface
The LinkarClt class is a primary interface between client and server, primarily responsible for sending and receiving LkData objects. There are two main usage patterns.
For both usage patterns, a CredentialsOptions object must be defined, containing details about the server, EntryPoint, and user+password.
•For Persistent sessions, a LinkarClt object is instantiated with an optional receiveTimeout value (see below). The Login method on that object is then called, passing in the CredentialsOptions to establish the connection. This is a "virtual" login to a started EntryPoint, not a login to the MV DBMS. A session ID is returned which will then accompany with all transactions from this object. In Linkar MANAGER, the Client Monitor shows the session ID for this client session until it is terminated. Operations are performed using methods on this object, until a final "virtual" Logout is executed which simply disposes the session ID. The DBMS connection linked with the EntryPoint remains intact.
Note again, the Database Session is available for all transactions from any client. The Database Session is not "busy" from start to finish while a single Client Session is active. Many clients can obtain a session ID simultaneously, and the Database Session is only occupied as each client performs a single transaction.
•For Direct/Volatile connections, static methods are called on the LinkarClt class. The CredentialsOptions object is passed with each transaction for a virtual login/logout. No session ID is generated or returned. In Linkar MANAGER, the Client Monitor shows these transactions as "VOLATILE". These transactions go through the same Database Sessions as Persistent sessions. The only difference is momentary nature of the Volatile session compared to the longer-term Persistent session.
Since a Persistent session has a single authentication for all subsequent transactions, it is much faster for a a number of transactions than the Direct sessions which need to re-authenticate with every connection.
See EntryPoint Configuration for more insight into session types.
receiveTimeout
|
Numeric |
Default 0 |
The maximum time in seconds that the client will wait for a server response in each transaction. Zero deactivates the timeout and the client will wait indefinitely for any single response. Individual transactions can specify their own timeout period, but they default back to this value. It is advisable to set this to a reasonable absolute maximum and override the timeout with a value that makes sense for each individual transaction. |
