summaryrefslogtreecommitdiff
path: root/docs/tutorials/010/page04.html
blob: 1a22e79347501469ac6d3002a58c55543324de3d (plain)
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
<HTML>
<HEAD>
   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
   <META NAME="Author" CONTENT="James CE Johnson">
   <TITLE>ACE Tutorial 010</TITLE>
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#000FFF" VLINK="#FF0F0F">

<CENTER><B><FONT SIZE=+2>ACE Tutorial 010</FONT></B></CENTER>

<CENTER><B><FONT SIZE=+2>Passing chunks of data through an ACE_Message_Queue</FONT></B></CENTER>


<HR WIDTH="100%">
<P>

Our <A HREF="task.h">Task</A> object executes in one or more threads
and reads from the message queue it contains.
<P>

<HR WIDTH="100%">
<PRE>

#include "ace/Task.h"

/*
  Like the thread-pool server tutorial, we'll derive from ACE_Task<>.
  Our goal here is to show off the ACE_Message_Queue and the best way
  to do that is to use one to pass data between threads.  The easiest
  way to create threads is with ACE_Task<>
 */
class Task : public ACE_Task < ACE_MT_SYNCH >
{
public:

  typedef ACE_Task < ACE_MT_SYNCH > inherited;
    
    /*
      The constructor/destructor are simple but take care of some
      necessary housekeeping.
    */
    Task (void);
   ~Task (void);

  /*
    To make our Task<> derivative look more like other ACE objects
    I've added an open() method.  It will take care of activate()ing
    the object.
  */
  int open (int threads = 1);

  /*
    Our worker method
  */
  int svc (void);

  /*
    All we'll do here is print a message to the user.
  */
  int close (u_long flags = 0);

protected:
    /*
      Just to be clever, I'll use an ACE_Barrier to cause the threads
      to sync in svc() before doing any real work.
    */
    ACE_Barrier *barrier_;
};
</PRE>
<HR WIDTH="100%">
<P>
The only thing here that we didn't see in the thread-pool server is the
ACE_Barrier.  The application logic really doesn't need it but it is a
handy way to synchronize the threads at the beginning of svc().  In testing
I found that if I didn't sync svc(), the first thread to get activated would
tend to get all of the messages before the other threads came alive.
<P>
<HR WIDTH="100%">

<CENTER>[<A HREF="..">Tutorial Index</A>] [<A HREF="page05.html">Continue
This Tutorial</A>]</CENTER>

</BODY>
</HTML>