1 files changed, 0 insertions, 65 deletions
diff --git a/docs/tutorials/010/page03.html b/docs/tutorials/010/page03.html
deleted file mode 100644
index 9c35bf18a86..00000000000
--- a/docs/tutorials/010/page03.html
+++ /dev/null
@@ -1,65 +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 010</TITLE>
-</HEAD>
-<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#000FFF" VLINK="#FF0F0F">
-
-<CENTER><B><FONT SIZE=+2>ACE Tutorial 010</FONT></B></CENTER>
-
-<CENTER><B><FONT SIZE=+2>Passing chunks of data through an ACE_Message_Queue</FONT></B></CENTER>
-
-
-<HR WIDTH="100%">
-<P>
-
-Our <A HREF="block.h">Block</A> object is a very simple derivative
-of the ACE_Message_Block.  The only reason I created it was to prove
-that the message blocks to, indeed, get freed when we're done with 'em.
-<P>
-
-<HR WIDTH="100%">
-<PRE>
-
-#include "ace/Message_Block.h"
-
-/*
-   This simple ACE_Message_Block derivative will inform us of it's construction 
-   and destruction.  We'll use this to assure ourselves that we don't have any
-   memory leaks.  In a real application, of course, this isn't necessary.
- */
-class Block : public ACE_Message_Block
-{
-public:
-  Block (void)
-  {
-    ACE_DEBUG ((LM_DEBUG, "(%P|%t) Block ctor 0x%x\n", (void *) this));
-  }
-
-  Block (size_t size)
-   : ACE_Message_Block (size)
-  {
-    ACE_DEBUG ((LM_DEBUG, "(%P|%t) Block ctor 0x%x\n", (void *) this));
-  }
-
-  virtual ~ Block (void)
-  {
-    ACE_DEBUG ((LM_DEBUG, "(%P|%t) Block dtor 0x%x\n", (void *) this));
-  }
-};
-
-</PRE>
-<HR WIDTH="100%">
-<P>
-Ok, nothing really magic there.  Some folks just feel a little uncomfortable
-not doing an explicit <i>delete</i> on objects they've <i>new</i>'d so I
-wanted to show you that the memory really does get cleaned up.
-<P>
-<HR WIDTH="100%">
-
-<CENTER>[<A HREF="..">Tutorial Index</A>] [<A HREF="page04.html">Continue
-This Tutorial</A>]</CENTER>
-
-</BODY>
-</HTML>