/usr/include/tao/Synch_Queued_Message.h is in libtao-dev 6.0.1-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 | // -*- C++ -*-
//=============================================================================
/**
* @file Synch_Queued_Message.h
*
* $Id: Synch_Queued_Message.h 81839 2008-06-05 11:58:32Z elliott_c $
*
* @author Carlos O'Ryan <coryan@uci.edu>
*/
//=============================================================================
#ifndef TAO_SYNCH_QUEUED_MESSAGE_H
#define TAO_SYNCH_QUEUED_MESSAGE_H
#include /**/ "ace/pre.h"
#include "tao/Queued_Message.h"
#if !defined (ACE_LACKS_PRAGMA_ONCE)
# pragma once
#endif /* ACE_LACKS_PRAGMA_ONCE */
TAO_BEGIN_VERSIONED_NAMESPACE_DECL
/**
* @class TAO_Synch_Queued_Message
*
* @brief Specialize TAO_Queued_Message for synchronous requests,
* i.e. twoways and oneways sent with reliability better than
* SYNC_NONE.
*
* Reliable requests block the sending thread until the message is
* sent, likewise, the sending thread must be informed if the
* connection is closed or the message times out.
*
* In contrast oneway (and AMI) requests sent with the SYNC_NONE
* policy are simple discarded if the connection fails or they
* timeout.
*
* Another important difference is the management of the data buffer:
* one SYNC_NONE messages the buffer is immediately copied into a
* newly allocated buffer, and must be deallocated. Other types of
* requests use the memory allocated by the sending thread.
*
*/
class TAO_Export TAO_Synch_Queued_Message : public TAO_Queued_Message
{
public:
/// Constructor
/**
* @param contents The message block chain that must be sent.
*
* @param alloc The allocator that is used to allocate objects of
* this type.
*/
TAO_Synch_Queued_Message (const ACE_Message_Block *contents,
TAO_ORB_Core *oc,
ACE_Allocator *alloc = 0,
bool is_heap_allocated = false);
/// Destructor
virtual ~TAO_Synch_Queued_Message (void);
const ACE_Message_Block *current_block (void) const;
/** @name Implement the Template Methods from TAO_Queued_Message
*/
//@{
virtual size_t message_length (void) const;
virtual int all_data_sent (void) const;
virtual void fill_iov (int iovcnt_max, int &iovcnt, iovec iov[]) const;
virtual void bytes_transferred (size_t &byte_count);
virtual TAO_Queued_Message *clone (ACE_Allocator *alloc);
virtual void destroy (void);
virtual void copy_if_necessary (const ACE_Message_Block* chain);
//@}
private:
/// The contents of the message.
/**
* The message is normally generated by a TAO_OutputCDR stream. The
* application marshals the payload, possibly generating a chain of
* message block connected via the 'cont()' field.
*/
ACE_Message_Block *contents_;
/// The current message block
/**
* The message may be set in multiple writev() operations. This
* point keeps track of the next message to send out.
*/
ACE_Message_Block *current_block_;
/// Do we own the contents_ message block?
/**
* This flag differs from the is_heap_allocated_ flag in that it only
* applies to the contents_ message block and not the
* TAO_Synch_Queued_Message object itself.
*/
bool own_contents_;
};
TAO_END_VERSIONED_NAMESPACE_DECL
#include /**/ "ace/post.h"
#endif /* TAO_QUEUED_MESSAGE_H */
|