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

# Pluggable_Messaging_Utils.h File Reference

`#include "tao/IOP_IORC.h"`
`#include "tao/Pluggable_Messaging_Utils.i"`

Include dependency graph for Pluggable_Messaging_Utils.h:

This graph shows which files directly or indirectly include this file:

## Classes
class | TAO_Pluggable_Reply_Params_Base
| TAO_Pluggable_Acceptor_Params. More...
class | TAO_Pluggable_Reply_Params
| TAO_Pluggable_Connector_Params. More...
## Enumerations
enum | TAO_Pluggable_Header_Type { TAO_PLUGGABLE_MESSAGE_REQUEST_HEADER = 0, TAO_PLUGGABLE_MESSAGE_LOCATE_REQUEST_HEADER }
enum | TAO_Pluggable_Message_Type { TAO_PLUGGABLE_MESSAGE_REQUEST = 0, TAO_PLUGGABLE_MESSAGE_REPLY = 1, TAO_PLUGGABLE_MESSAGE_CANCELREQUEST = 2, TAO_PLUGGABLE_MESSAGE_LOCATEREQUEST = 3, TAO_PLUGGABLE_MESSAGE_LOCATEREPLY = 4, TAO_PLUGGABLE_MESSAGE_CLOSECONNECTION = 5, TAO_PLUGGABLE_MESSAGE_MESSAGERROR = 6, TAO_PLUGGABLE_MESSAGE_FRAGMENT = 7 }
enum | TAO_Pluggable_Message_Exception_Type { TAO_PLUGGABLE_MESSAGE_NO_EXCEPTION = 0, TAO_PLUGGABLE_MESSAGE_USER_EXCEPTION, TAO_PLUGGABLE_MESSAGE_SYSTEM_EXCEPTION, TAO_PLUGGABLE_MESSAGE_LOCATION_FORWARD, TAO_PLUGGABLE_MESSAGE_LOCATION_FORWARD_PERM, TAO_PLUGGABLE_MESSAGE_NEEDS_ADDRESSING_MODE }

## Detailed Description

Id
  Pluggable_Messaging_Utils.h,v 1.22 2005/11/02 11:03:26 ossama Exp

Utility classes for the TAO pluggable messaging framework.

Author:
  Balachandran Natarajan <bala@cs.wustl.edu>

## Enumeration Type Documentation

enum TAO_Pluggable_Header_Type

  | Enumeration values:
  TAO_PLUGGABLE_MESSAGE_REQUEST_HEADER |
  TAO_PLUGGABLE_MESSAGE_LOCATE_REQUEST_HEADER |

enum TAO_Pluggable_Message_Exception_Type

  | Provide an external interface for the users of this pluggable messaging framework to denote existing Exception types. This has an inspiration from GIOP. So if anybody wants to add more message types you are welcome but please do not change the numbering scheme as this would affect GIOP. Enumeration values:
  TAO_PLUGGABLE_MESSAGE_NO_EXCEPTION | Request completed successfully.
  TAO_PLUGGABLE_MESSAGE_USER_EXCEPTION | Request terminated with user exception.
  TAO_PLUGGABLE_MESSAGE_SYSTEM_EXCEPTION | Request terminated with system exception.
  TAO_PLUGGABLE_MESSAGE_LOCATION_FORWARD | Reply is a location forward type.
  TAO_PLUGGABLE_MESSAGE_LOCATION_FORWARD_PERM | PLUGGABLE_MESSAGE 1.2, Reply is a location forward perm type..
  TAO_PLUGGABLE_MESSAGE_NEEDS_ADDRESSING_MODE | GIOP1.2,.

enum TAO_Pluggable_Message_Type

  | Provide an external interface for the users of this pluggable messaging framework to denote existing message types. This has an inspiration from GIOP. So if anybody wants to add more message types you are welcome but please do not change the numbering scheme as this would affect GIOP. Note: We may not need everything here. It would be good if we have only the following messages TAO_PLUGGABLE_MESSAGE_REQUEST, TAO_PLUGGABLE_MESSAGE_REPLY, TAO_PLUGGABLE_MESSAGE_CLOSECONNECTION, TAO_PLUGGABLE_MESSAGE_MESSAGE_ERROR. Changes will be made once the rest of the stuff gets ready to roll Enumeration values:
  TAO_PLUGGABLE_MESSAGE_REQUEST |
  TAO_PLUGGABLE_MESSAGE_REPLY |
  TAO_PLUGGABLE_MESSAGE_CANCELREQUEST |
  TAO_PLUGGABLE_MESSAGE_LOCATEREQUEST |
  TAO_PLUGGABLE_MESSAGE_LOCATEREPLY |
  TAO_PLUGGABLE_MESSAGE_CLOSECONNECTION |
  TAO_PLUGGABLE_MESSAGE_MESSAGERROR |
  TAO_PLUGGABLE_MESSAGE_FRAGMENT |