NetTransport
Class
Superclasses
System.Object
Transport
NetTransport
Visual Basic
Public ClassNetTransport
Inherits Transport
C#
public class NetTransport : Transport
Purpose
Deliver messages across a network.
Remarks
Programs must explicitly destroy instances of this class. Rendezvous software keeps internal references to these objects, so the garbage collector does not delete them automatically.
|
Member |
Description |
|
Public Instance Properties |
||
|
The socket where the transport connects to the Rendezvous daemon. |
Set |
|
|
The socket where the transport connects to the Rendezvous daemon. |
Get |
|
The description identifies programs and their transports to Rendezvous components. Browser administration interfaces display the description string. As a debugging aid, we recommend setting a unique description string for each transport. Use a string that distinguishes both the application and the role of the transport within it. |
Get Set |
|
The network interface that the transport uses for communication. |
Get |
|
Set this property to request a reliability interval (message retention time, in seconds) for the transport’s service. This value must be greater than zero. For details, see Reliability. |
Set |
|
The effective service that the transport uses for communication. |
Get |
|
Method |
Description |
Page |
Remarks
This class is the superclass of other network transport classes.
|
Inherited Methods |
Reliability
Setting the Reliability property (in seconds) lets application programs shorten the reliability interval of the specific service associated with a transport object. Successfully setting this property changes the daemon’s reliability interval for all transports within the application process that use the same service.
Programs can request reliability only from daemons of release 8.2 or later.
An application can request a shorter retention time than the value that governs the daemon as a whole (either the factory default or the daemons -reliability parameter). The daemon’s governing value silently overrides requests for a longer retention time.
Client transport objects that connect to the same daemon could specify different reliability intervals on the same service—whether by requesting a reliability value, or by using the daemon’s effective value. In this situation, the daemon selects the largest potential value from among all the transports on that service, and uses that maximum value as the effective reliability interval for the service (that is, for all the transports on the service). This method of resolution favors the more stringent reliability requirements. (Contrast this rule with the Lower Value Rule that applies between two daemons.)
Whenever a transport connects, requests reliability, or disconnects from the daemon, the daemon recalculates the reliability interval for the corresponding service, by selecting the largest value of all transports communicating on that service.
When recomputing the reliability interval would result in a shorter retention time, the daemon delays using the new value until after an interval equivalent to the older (longer) retention time. This delay ensures that the daemon retains message data at least as long as the effective reliability interval at the time the message is sent.
Related Classes
See Also
Reliability and Message Retention Time in
Lower Value Rule in
Changing the Reliability Interval within an Application Program in
Reliable Message Delivery in