Main Page | Namespace List | Class Hierarchy | Alphabetical List | Class List | Directories | File List | Namespace Members | Class Members | File Members

# TAO::SL3::SecurityCurrent Class Reference

SecurityLevel3::SecurityCurrent implementation. More...

`#include <SL3_SecurityCurrent.h>`

Inheritance diagram for TAO::SL3::SecurityCurrent:

[legend]
Collaboration diagram for TAO::SL3::SecurityCurrent:

[legend]
List of all members.

## Public Member Functions
| SecurityCurrent (size_t tss_slot, TAO_ORB_Core *oc)
| Constructor.
size_t | tss_slot (void) const
SecurityLevel3::SecurityCurrent Methods
Methods required by the SecurityLevel3::SecurityCurrent interface.
virtual SecurityLevel3::ClientCredentials_ptr | client_credentials (ACE_ENV_SINGLE_ARG_DECL) throw (CORBA::SystemException)
virtual CORBA::Boolean | request_is_local (ACE_ENV_SINGLE_ARG_DECL) throw (CORBA::SystemException)
## Protected Member Functions
| ~SecurityCurrent (void)
| Destructor.
## Private Member Functions
SecurityCurrent_Impl * | implementation (void)
Retricted Copying and Assignment
Prevent copying through the copy constructor and the assignment operator.
| SecurityCurrent (const SecurityCurrent &)
void | operator= (const SecurityCurrent &)
## Private Attributes
const size_t | tss_slot_
| Thread-specific storage slot assigned to this object.
TAO_ORB_Core *const | orb_core_

## Detailed Description

SecurityLevel3::SecurityCurrent implementation.

Thread-specific information may be retrieved from the target security service through this object.

Note:
  This SecurityCurrent implementation basically a variant of the bridge design pattern. All operations are delegated on to concrete implementations.

## Constructor & Destructor Documentation

TAO_BEGIN_VERSIONED_NAMESPACE_DECL TAO::SL3::SecurityCurrent::SecurityCurrent | ( | size_t | tss_slot,
|  | TAO_ORB_Core * | oc
| ) |

| Constructor.

TAO::SL3::SecurityCurrent::~SecurityCurrent | ( | void |  | ) | `[protected]`

| Destructor. Protected destructor to enforce proper memory management through the reference counting mechanism.

TAO::SL3::SecurityCurrent::SecurityCurrent | ( | const SecurityCurrent & |  | ) | `[private]`

## Member Function Documentation

virtual SecurityLevel3::ClientCredentials_ptr TAO::SL3::SecurityCurrent::client_credentials | ( | ACE_ENV_SINGLE_ARG_DECL |  | ) | throw (CORBA::SystemException)`[virtual]`

ACE_INLINE TAO::SL3::SecurityCurrent_Impl * TAO::SL3::SecurityCurrent::implementation | ( | void |  | ) | `[private]`

| The pointer is actually one to a concrete implementation provided by the underlying security mechanism. For example, SSLIOP implements its own SSLIOP-specific operations corresponding to the ones exposed by the SecurityCurrent interface. Similarly, SECIOP would do the same. There is no function that places the implementation pointer in TSS. The underlying security mechanism does that.

void TAO::SL3::SecurityCurrent::operator= | ( | const SecurityCurrent & |  | ) | `[private]`

virtual CORBA::Boolean TAO::SL3::SecurityCurrent::request_is_local | ( | ACE_ENV_SINGLE_ARG_DECL |  | ) | throw (CORBA::SystemException)`[virtual]`

TAO_BEGIN_VERSIONED_NAMESPACE_DECL ACE_INLINE size_t TAO::SL3::SecurityCurrent::tss_slot | ( | void |  | ) | const

| The concrete thread-specific storage SecurityCurrent implementations will each use this slot ID.

## Member Data Documentation

TAO_ORB_Core* const TAO::SL3::SecurityCurrent::orb_core_`[private]`

| Pointer to the ORB Core corresponding to the ORB with which this object is registered. Reimplemented from CORBA::Object.

const size_t TAO::SL3::SecurityCurrent::tss_slot_`[private]`

| Thread-specific storage slot assigned to this object.

The documentation for this class was generated from the following files:

- SL3_SecurityCurrent.h
- SL3_SecurityCurrent.cpp
- SL3_SecurityCurrent.inl