1 files changed, 0 insertions, 41 deletions
diff --git a/docs/tutorials/015/page01.html b/docs/tutorials/015/page01.html
deleted file mode 100644
index 7d8f425b972..00000000000
--- a/docs/tutorials/015/page01.html
+++ /dev/null
@@ -1,41 +0,0 @@
-<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%">
-
-In a typical client/server system you will be sending and receiving
-      data.  That's the whole point after all.
-<P>
-In the client/server tutorials that we've done so far it was just a
-      matter of sending a buffer of data to the peer.  This was done
-      with the send*() and recv*() methods of the ACE_SOCK* objects.
-<P>
-In a more robust system, one might want to process the data before
-      sending it to a peer and "unprocess" it after reading from a
-      peer.  These processing steps might include encryption,
-      compression, applying checksums or any number of other actions.
-<P>
-In this tutorial a Protocol_Stream object is created to encrypt and
-      compress* data being sent between peers.  Both client and server 
-      applications are presented as well.  I present the application
-level code first and then go into the details of the protocol stream
-and it's helper objects.  If the stream stuff in the application logic 
-is confusing then just read on by and come back to it after the later
-discussions.
-
-<P>
-<font size=-1>* Ok, I didn't really implement encryption and
-        compression objects.  I'll leave that as a thought
-        exercise!</font>
-<P><HR WIDTH="100%">
-<CENTER>[<A HREF="../online-tutorials.html">Tutorial Index</A>] [<A HREF="page02.html">Continue This Tutorial</A>]</CENTER>