Virtual Circuit API

The virtual circuit API consists of three calls (see Virtual Circuit Calls) and two advisory messages.

Create Terminals

Two calls create the terminal objects—one call for the terminal that accepts connections, and one for the terminal that subsequently connects to it.

The two types of terminal play complementary protocol roles as they attempt to establish a connection. However, this difference soon evaporates. After the connection is complete, the two terminals behave identically.

Testing the Connection

A third call tests the current status of the connection. Programmers can arrange for this call to return immediately, or block until the connection is complete (wait for connection).

Other Transport Calls

Programs send messages, create inbox names, and create listeners using the same calls as for ordinary transports.

Virtual Circuit Calls
C	`tibrvTransport_CreateAcceptVc()` `tibrvTransport_CreateConnectVc()` `tibrvTransport_WaitForVcConnection()`
C++	`TibrvVcTransport` `TibrvVcTransport::createAcceptVc()` `TibrvVcTransport::createConnectVc()` `TibrvVcTransport::waitForVcConnection()`
Java	`TibrvVcTransport` `TibrvVcTransport.createAcceptVc()` `TibrvVcTransport.createConnectVc()` `TibrvVcTransport.waitForVcConnection()`
.NET	`VCTransport.CreateAcceptVC` `VCTransport.CreateConnectVC` `VCTransport.WaitForVCConnection`

Advisories

Advisory messages report connection status changes asynchronously; see VC.CONNECTED, and VC.DISCONNECTED.

Did you find this helpful?

Yes No