<!-- page03.html,v 1.11 2000/03/19 20:09:22 jcej Exp --> <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="Billy Quinn"> <META NAME="Description" CONTENT="A first step towards using ACE productively"> <TITLE>ACE Tutorial 005</TITLE> </HEAD> <BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#000FFF" VLINK="#FF0F0F"> <CENTER><B><FONT SIZE=+2>ACE Tutorial 005</FONT></B></CENTER> <CENTER><B><FONT SIZE=+2>On the road to a multithreaded server</FONT></B></CENTER> <P> <HR WIDTH="100%"> <P>Now, let's take a look at <I><A HREF="client_acceptor.h">client_acceptor.h</A></I>. Since I went on about how it does all the work of letting clients connect to us, it must be rather complex. Right? Wrong. <P>The more you use ACE, the more you'll find that they've already taken care of most details for you. With respect to the acceptance of client connections: there just aren't that many ways to do it! The ACE team has chosen an approach and created a C++ template that does all of the work for you. All you're required to do is provide it with an object type to instantiate when a new connection arrives. <P> <HR WIDTH="100%"> <PRE> <font color=red>// page03.html,v 1.11 2000/03/19 20:09:22 jcej Exp</font> <font color=blue>#ifndef</font> <font color=purple>CLIENT_ACCEPTOR_H</font> <font color=blue>#define</font> <font color=purple>CLIENT_ACCEPTOR_H</font> <font color=red>/* The ACE_Acceptor<> template lives in the ace/Acceptor.h header file. You'll find a very consitent naming convention between the ACE objects and the headers where they can be found. In general, the ACE object ACE_Foobar will be found in ace/Foobar.h. */</font> <font color=blue>#include</font> "<A HREF="../../../ace/Acceptor.h">ace/Acceptor.h</A>" <font color=blue>#if !defined</font> (<font color=purple>ACE_LACKS_PRAGMA_ONCE</font>) <font color=blue># pragma</font> <font color=purple>once</font> <font color=blue>#endif</font> <font color=red>/* ACE_LACKS_PRAGMA_ONCE */</font> <font color=red>/* Since we want to work with sockets, we'll need a SOCK_Acceptor to allow the clients to connect to us. */</font> <font color=blue>#include</font> "<A HREF="../../../ace/SOCK_Acceptor.h">ace/SOCK_Acceptor.h</A>" <font color=red>/* The Client_Handler object we develop will be used to handle clients once they're connected. The ACE_Acceptor<> template's first parameter requires such an object. In some cases, you can get by with just a forward declaration on the class, in others you have to have the whole thing. */</font> <font color=blue>#include</font> "<font color=green>client_handler.h</font>" <font color=red>/* Parameterize the ACE_Acceptor<> such that it will listen for socket connection attempts and create Client_Handler objects when they happen. In Tutorial 001, we wrote the basic acceptor logic on our own before we realized that ACE_Acceptor<> was available. You'll get spoiled using the ACE templates because they take away a lot of the tedious details! */</font> typedef ACE_Acceptor <Client_Handler, ACE_SOCK_ACCEPTOR> Client_Acceptor; <font color=blue>#endif</font> <font color=red>/* CLIENT_ACCEPTOR_H */</font> </PRE> <P><HR WIDTH="100%"> <CENTER>[<A HREF="../online-tutorials.html">Tutorial Index</A>] [<A HREF="page04.html">Continue This Tutorial</A>]</CENTER>