TAO_SCIOP_Profile Class ReferenceThis class defines the protocol specific attributes required for locating ORBs over a TCP/IP network. More...
Inheritance diagram for TAO_SCIOP_Profile:
Collaboration diagram for TAO_SCIOP_Profile:
Detailed DescriptionThis class defines the protocol specific attributes required for locating ORBs over a TCP/IP network.This class defines the SCIOP profile as specified in the CORBA specification. Constructor & Destructor Documentation
Profile constructor, same as above except the object_key has already been marshaled.
Profile constructor, this is the most efficient since it doesn't require any address resolution processing.
Profile constructor, default.
Destructor is to be called only through <_decr_refcnt>.
Member Function Documentation
Implements TAO_Profile.
Return the char string prefix.
Implements TAO_Profile.
Implements TAO_Profile.
Implements TAO_Profile.
Implements TAO_Profile.
Add <endp> to this profile's list of endpoints (it is inserted next to the head of the list). This profiles takes ownership of <endp>.
Implements TAO_Profile.
Implements TAO_Profile.
Implements TAO_Profile.
Implements TAO_Profile.
Member Data Documentation
The object key delimiter that SCIOP uses or expects.
Head of this profile's list of endpoints. This endpoint is not dynamically allocated because a profile always contains at least one endpoint. Currently, a profile contains more than one endpoint, i.e., list contains more than just the head, only for two cases (1) when RTCORBA is enabled and (2) the ORB is initialized with -ORBPreferredInterfaces option. However, in the near future, this will be used in for mode as well, e.g., to support TAG_ALTERNATE_IIOP_ADDRESS feature. This is probably as good a place to discuss how the list of endpoints is used for #2. If the ORB is configured to use preferred interfaces for invocation, TAO creates an endpoint per preferred interface. To be clear, every tuple <destination:target> will have an endpoint. What TAO essentially does is that creates it multiple endpoints so that the invocation code path can use existing iterating techniques to try one preferred interface after another (if the first did not work). If the ORB is configured with -ORBEnforcePreferredInterface set to false in addition to the ORBPreferredInterfaces option , TAO creates another endpoint with the preferred bit set to null, so that the invocation code can fall back to a SCTP stack returned local address. Addressing info of the default endpoint, i.e., head of the list, is transmitted using standard SCIOP ProfileBody components. See <encode_endpoints> method documentation above for how the rest of the endpoint list is transmitted.
Number of endpoints in the list headed by <endpoint_>.
The documentation for this class was generated from the following files: Generated on Mon Sep 15 08:30:56 2008 for TAO_Strategies by 1.5.5 |