Open topic with navigation

TIBCO Rendezvous® 8.7.0

# TibrvVcTransport

Class

## Declaration

    class TibrvVcTransport : public TibrvTransport
        TibrvVcTransport();           // Construct empty.
        virtual ~TibrvVcTransport();  // Destroy and reclaim storage.

## Purpose

A virtual circuit transport object represents a terminal in a potential circuit.

## Remarks

A virtual circuit transport can fill the same roles as an ordinary transport. Programs can use them to create inbox names, send messages, create listeners and other events.

The constructor creates a hollow object; programs call one of the two create methods to makes operational.

The destructor calls the `destroy` method, unless the C object is already destroyed.

Two methods determine the protocol role of the transport object—one method creates a terminal that accepts connections, and another method creates a terminal that attempts to connect.

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

Method | Description
TibrvVcTransport::createAcceptVc() | Create a virtual circuit accept object.
TibrvVcTransport::createConnectVc() | Create a virtual circuit connect object.
TibrvVcTransport::waitForVcConnection() | Test the connection status of a virtual circuit.

## Broken Connection

The following conditions can close a virtual circuit connection:

| • | Contact is broken between the object and its terminal.

| • | The virtual circuit loses data in either direction (see DATALOSS in TIBCO Rendezvous Concepts).

| • | The partner program destroys its terminal object (or that terminal becomes invalid).

| • | The program destroys the object.

| • | The program destroys the object’s ordinary transport.

## Destroying VC Transports

Destroying a transport object precludes subsequent communications on that transport. Attempting to use a destroyed transport in any way is an error.

Destroying a virtual circuit transport does not affect the ordinary transport that the terminal employs.

To free storage, call the object’s destructor. (The destroy method does not automatically free storage.)

## Direct Communication

Because virtual circuits rely on point-to-point messages between the two terminals, they can use direct communication to good advantage. To do so, both terminals must use network transports that enable direct communication.

For an overview, see Direct Communication in TIBCO Rendezvous Concepts.

For programming details, see Specifying Direct Communication in TIBCO Rendezvous Concepts.

Inherited Methods
Legal Methods | TibrvTransport::createInbox() TibrvTransport::destroy() TibrvTransport::getHandle() TibrvTransport::isValid() TibrvTransport::send() TibrvTransport::sendReply() TibrvTransport::sendRequest()
Disabled Methods | TibrvTransport::getDescription() TibrvTransport::setDescription()

## See Also

Virtual Circuits in TIBCO Rendezvous Concepts

Subtopics

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO Rendezvous®

Copyright © 1997-2023. Cloud Software Group, Inc. All Rights Reserved.