summaryrefslogtreecommitdiff
path: root/docs/tutorials/015/page12.html
blob: 99d3959582dd1799835508b5317b30763d367157 (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
85
86
87
88
89
90
91
92
93
94
<HTML>
<HEAD>
   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
   <META NAME="Author" CONTENT="James CE Johnson">
   <TITLE>ACE Tutorial 015</TITLE>
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#000FFF" VLINK="#FF0F0F">

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

<CENTER><B><FONT SIZE=+2>Building a protocol stream</FONT></B></CENTER>

<P>
<HR WIDTH="100%">
And now the implementation of the Protocol_Stream.  There are more
lines of code here than we've seen so far but it still isn't
complicated.  The basic idea is to construct the ACE_Stream with our
set of protocol objects that will manipulate the data.  Our primary
concern in this file is to get everything in the correct order!
<HR>
<PRE>
<font color=red>// $Id$</font>

<font color=blue>#ifndef</font> <font color=purple>PROTOCOL_TASK_H</font>
<font color=blue>#define</font> <font color=purple>PROTOCOL_TASK_H</font>

<font color=blue>#include</font> "<font color=green>ace/Task.h</font>"

<font color=blue>#if !defined</font> (<font color=purple>ACE_LACKS_PRAGMA_ONCE</font>)
# pragma once
<font color=blue>#endif</font> <font color=red>/* ACE_LACKS_PRAGMA_ONCE */</font>

<font color=red>/* A typical ACE_Task&lt;> derivative that adds a few things appropriate
   to protocol stacks.
*/</font>
class Protocol_Task : public ACE_Task&lt;ACE_MT_SYNCH>
{
public:
  typedef ACE_Task&lt;ACE_MT_SYNCH> inherited;

  <font color=red>// A choice of concurrency strategies is offered by the constructor.</font>
  <font color=red>// In most cases it makes sense to set this to zero and let things</font>
  <font color=red>// proceed serially.  You might have a need, however, for some of</font>
  <font color=red>// your tasks to have their own thread.</font>
  Protocol_Task (int thr_count);

  ~Protocol_Task (void);

  <font color=red>// open() is invoked when the task is inserted into the stream.</font>
  virtual int open (void *arg);

  <font color=red>// close() is invoked when the stream is closed (flags will be set</font>
  <font color=red>// to '1') and when the svc() method exits (flags will be '0').</font>
  virtual int close (u_long flags);

  <font color=red>// As data travels through the stream, the put() method of each task</font>
  <font color=red>// is invoked to keep the data moving along.</font>
  virtual int put (ACE_Message_Block *message,
                   ACE_Time_Value *timeout);

  <font color=red>// If you choose to activate the task then this method will be doing</font>
  <font color=red>// all of the work.</font>
  virtual int svc (void);

protected:

  <font color=red>// Called by put() or svc() as necessary to process a block of data.</font>
  int process (ACE_Message_Block *message,
               ACE_Time_Value *timeout);

  <font color=red>// Just let us know if we're active or not.</font>
  int is_active (void)
  {
    return this->thr_count () != 0;
  }

  <font color=red>// Tasks on the writter (downstream) side of the stream are called</font>
  <font color=red>// upon to send() data that will ultimately go to the peer.</font>
  virtual int send (ACE_Message_Block *message,
                    ACE_Time_Value *timeout);

  <font color=red>// Tasks on the reader (upstream) side will be receiving data that</font>
  <font color=red>// came from the peer.</font>
  virtual int recv (ACE_Message_Block *message,
                    ACE_Time_Value *timeout);

private:
  int desired_thr_count_;
};

<font color=blue>#endif</font> <font color=red>/* PROTOCOL_TASK_H */</font>
</PRE>
<P><HR WIDTH="100%">
<CENTER>[<A HREF="../online-tutorials.html">Tutorial Index</A>] [<A HREF="page13.html">Continue This Tutorial</A>]</CENTER>