#include <SSLIOP_Profile.h>
Inheritance diagram for TAO_SSLIOP_Profile:
This class extends TAO_IIOP_Profile to support secure communication using SSL.
|
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. |
|
Create profile with the given SSLIOP tagged component.
|
|
Profile constructor, default.
|
|
Destructor is to be called only through _decr_refcnt().
|
|
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>. If <endp>'s <iiop_endpoint_> member is not 0, it is added to our parent's class endpoint list. |
|
Reimplemented from TAO_Profile. |
|
Helper for <decode>. Decodes TAO_TAG_SSL_ENDPOINTS from a tagged component. Decode only if RTCORBA is enabled. Return 0 on success and -1 on failure. @NOTE: This should be enabled only when RTCORBA is enabled, but sadly others pay the price (of footprint) under normal operations. |
|
Profile equivalence template method.
Reimplemented from TAO_IIOP_Profile. |
|
Reimplemented from TAO_IIOP_Profile. |
|
Reimplemented from TAO_IIOP_Profile. |
|
Override parse_string() from the base class to update the ssl endpoint's iiop endpoint once the base class has completed parsing the string. Initialize this object using the given input string. Url-style string contain only one endpoint. Reimplemented from TAO_Profile. |
|
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 when RTCORBA is enabled. However, in the near future, this will be used in nonRT mode as well, e.g., to support TAG_ALTERNATE_IIOP_ADDRESS feature. Since SSLIOP profile is an extension of IIOP profile, its addressing info is contained in two places: IIOP parent class contains all iiop addressing while this class contains ssl-specific addressing additions to iiop. This means that there are two lists of endpoints: one maintained in the parent class and one maintained here. Each ssl endpoint maintains a pointer to its counterpart in the parent class endpoint list. For transmission of iiop addressing information, see TAO_IIOP_Profile. Addressing info of the default ssl endpoint, i.e., head of the list, is transmitted using standard SSLIOP::TAG_SSL_SEC_TRANS tagged component. See <encode_endpoints> method documentation above for how the rest of the ssl endpoint list is transmitted. |