summaryrefslogtreecommitdiff
path: root/docs/tutorials/index.html
blob: 2cf27a9cb1f2a63821e5b4f00164830633c46f45 (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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
   <TITLE>ACE Tutorial Introduction</TITLE>
   <META NAME="GENERATOR" CONTENT="Mozilla/3.01Gold (Win95; I) [Netscape]">
   <META NAME="Author" CONTENT="James CE Johnson">
</HEAD>
<BODY text = "#000000" link="#000fff" vlink="#ff0f0f" bgcolor="#ffffff">


<HR><P>
<H3>ACE Tutorials</H3>

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

The original audience for these tutorials was the <A
HREF="http://www.lads.com">Automated Design Systems</A> (ADS) IPC
team, lead by <A HREF="mailto:jcej@lads.com">James Johnson</A>.  Since
then, the scope has been changed to include anyone who wants to learn
about the ACE framework.  Hopefully, even experienced ACE programmers
will find something new here.  With a framework as encompassing as
ACE, it is easy to become an expert in one area and know little or
nothing about others. <P>

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

<H3>What is ACE?</H3>

The <A HREF="http://www.cs.wustl.edu/~schmidt/ACE.html">ACE</a>
framework was developed mostly by <A
HREF="http://www.cs.wustl.edu/~schmidt">Douglas C. Schmidt's</A> team
at Washington University. The framework attempts to abstract the
details of many things across many operating systems. Some of the
things abstracted include: network programming, multi-threading,
shared memory and resource locking. 
<!--#include virtual="/~schmidt/ACE-versions-i.html" -->

<H3>Why Use ACE?</H3>

A key reason to use ACE is simple: <EM>write a multi-threaded
networked application on one platform and quickly be able to use it on
another</EM>. This is important for many projects because it is
necessary for applications to communicate with one another.  For
instance, many applications will exist on both UNIX and Win32
platforms within a local area network.</P>

<H3>What about TAO?</H3>

<P>In the early stages, these tutorials won't address The ACE ORB (<A
HREF="http://www.cs.wustl.edu/~schmidt">TAO</A>).  However, if you
want to request a tutorial on some aspect of TAO or even create one
yourself, I'll be glad to integrate those into these tutorials.  It's
rare when folks want to write documentation, so nothing will be
refused!  </P>

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

<H3>The Tutorials</H3>

<OL>
<LI><A HREF="001/page01.html">A Simple Server</A></LI>

<LI><A HREF="002/page01.html">A Simpler Server</A></LI>

<LI><A HREF="003/page01.html">Finally, a Client</A></LI>
<LI><A HREF="004/page01.html">A much <I>cooler</I> client</A></LI>

<LI><A HREF="005/page01.html">A server that handles it's connections in dedicated threads</A></LI>
<LI><A HREF="006/index.html">Like #5 but each thread can handle multiple connections</A></LI>

<LI><A HREF="007/">A client that forces all connection activities into a dedicated thread</A></LI>
<LI><A HREF="008/">A melding of #6 and #7</A></LI>

<LI>Next Tutorial</LI>
</OL>


<P><HR><P>

Back to the <A
HREF="http://www.cs.wustl.edu/~schmidt/ACE_wrappers/etc/ACE-tutorials.html">ACE
tutorials</A> page.

<!--#include virtual="/~schmidt/cgi-sig.html" -->
</BODY>
</HTML>