qpid::client Namespace Reference

The client namespace contains all classes that make up a client implementation of the AMQP protocol. More...


Classes

class  Session_0_10
 AMQP 0-10 session API with keyword arguments. More...
class  AckPolicy
 Policy for automatic acknowledgement of messages. More...
class  Channel
 THIS CLASS IS DEPRECATED AND WILL BE SHORTLY REMOVED. More...
class  Connection
 Represents a connection to an AMQP broker. More...
struct  ConnectionSettings
 Used to hold seetings for a connection (and parse these from command line oprions etc as a convenience). More...
class  Exchange
 DEPRECATED. More...
class  Execution
 Provides access to more detailed aspects of the session implementation. More...
class  LocalQueue
 Local representation of a remote queue. More...
class  Message
 A representation of messages sent or received through the client api. More...
class  MessageListener
 An interface through which asynchronously delivered messages can be received by an application. More...
class  MessageQueue
 A MessageListener implementation that queues up messages. More...
class  Queue
 DEPRECATED. More...
class  SessionBase
 Basic session operations that are not derived from AMQP XML methods. More...
class  SubscriptionManager
 Utility to assist with creating subscriptions. More...

Typedefs

typedef framing::Handler
< framing::FrameSet
FrameSetHandler
typedef Session_0_10 Session
 Session is currently just an alias for Session_99_0.

Enumerations

enum  AckMode { NO_ACK = 0, AUTO_ACK = 1, LAZY_ACK = 2, CLIENT_ACK = 3 }
 DEPRECATED. More...
enum  CreditUnit { MESSAGE = 0, BYTE = 1 }
enum  SynchronousMode { SYNC = true, ASYNC = false }

Functions

std::ostream & operator<< (std::ostream &, const Bounds &)


Detailed Description

The client namespace contains all classes that make up a client implementation of the AMQP protocol.

The key classes that form the basis of the client API to be used by applications are Connection and Channel.


Enumeration Type Documentation

DEPRECATED.

The available acknowledgement modes for Channel (now also deprecated).

Enumerator:
NO_ACK  No acknowledgement will be sent, broker can discard messages as soon as they are delivered to a consumer using this mode.

AUTO_ACK  Each message will be automatically acknowledged as soon as it is delivered to the application.

LAZY_ACK  Acknowledgements will be sent automatically, but not for each message.

CLIENT_ACK  The application is responsible for explicitly acknowledging messages.


Generated on Thu May 15 22:23:54 2008 for Qpid by  doxygen 1.5.5