summaryrefslogtreecommitdiff
path: root/docs/tutorials/007/page04.html
blob: 7a693d64a6f6ce651748a2aa0d41240d72cac951 (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
95
96
<HTML>
<HEAD>
   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
   <META NAME="GENERATOR" CONTENT="Mozilla/4.04 [en] (X11; I; Linux 2.0.32 i486) [Netscape]">
   <META NAME="Author" CONTENT="James CE Johnson">
   <META NAME="Description" CONTENT="A first step towards using ACE productively">
   <TITLE>ACE Tutorial 007</TITLE>
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#000FFF" VLINK="#FF0F0F">

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

<CENTER><B><FONT SIZE=+2>Creating a thread-pool server</FONT></B></CENTER>
<HR>

<P>Something new this time is <A HREF="client_acceptor.cpp">client_acceptor.cpp</A>.&nbsp;
I finally had enough code to move it out of the header.

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

<font color=red>// $Id$</font>

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

<font color=red>/*
   Construct ourselves with the chosen concurrency strategy.  Notice that we also
   set our Thread_Pool reference to our private instance.
 */</font>
<font color=#008888>Client_Acceptor::Client_Acceptor</font>( int _concurrency )
 :  concurrency_(_concurrency)
   ,the_thread_pool_(private_thread_pool_)
{
}

<font color=red>/*
   Construct ourselves with a reference to somebody else' Thread_Pool.  Obvioulsy
   our concurrency strategy is "<font color=green>thread_pool_</font>" at this point.
 */</font>
<font color=#008888>Client_Acceptor::Client_Acceptor</font>( Thread_Pool & _thread_pool )
 :  concurrency_(thread_pool_)
   ,the_thread_pool_(_thread_pool)
{
}

<font color=red>/*
   When we're destructed, we may need to cleanup after ourselves.  If we're running
   with a thread pool that we own, it is up to us to close it down.
 */</font>
<font color=#008888>Client_Acceptor::~Client_Acceptor</font>( void )
{
	if( this->concurrency() == thread_pool_ && thread_pool_is_private() )
	{
		thread_pool()->close();
	}
}

<font color=red>/*
   Similar to the destructor (and close() below) it is necessary for us to open the
   thread pool in some circumstances.

   Notice how we delegate most of the open() work to the open() method of our baseclass.
 */</font>
int <font color=#008888>Client_Acceptor::open</font>( const ACE_INET_Addr & _addr, ACE_Reactor * _reactor, int _pool_size )
{
	if( this->concurrency() == thread_pool_ && thread_pool_is_private() )
	{
		thread_pool()->open(_pool_size);
	}

	return <font color=#008888>inherited::open</font>(_addr,_reactor);
}

<font color=red>/*
   Here again we find that we have to manage the thread pool.  Like open() we also delegate
   the other work to our baseclass.
 */</font>
int <font color=#008888>Client_Acceptor::close</font>(void)
{
	if( this->concurrency() == thread_pool_ && thread_pool_is_private() )
	{
		thread_pool()->close();
	}

	return <font color=#008888>inherited::close</font>();
}

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

<P>Nothing really surprising here.&nbsp; Most of it just manages the Thread_Pool.

<P>
<P><HR WIDTH="100%">
<CENTER>[<A HREF="../online-tutorials.html">Tutorial Index</A>] [<A HREF="page05.html">Continue This Tutorial</A>]</CENTER>