You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by do...@apache.org on 2002/05/22 16:03:11 UTC

cvs commit: jakarta-avalon-phoenix/src/xdocs guide-architecture.xml

donaldp     02/05/22 07:03:11

  Modified:    src/xdocs Tag: ANAKIA_DOCS guide-architecture.xml
  Log:
  Reincorporate images
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.1.2.4   +8 -16     jakarta-avalon-phoenix/src/xdocs/guide-architecture.xml
  
  Index: guide-architecture.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/guide-architecture.xml,v
  retrieving revision 1.1.2.3
  retrieving revision 1.1.2.4
  diff -u -r1.1.2.3 -r1.1.2.4
  --- guide-architecture.xml	21 May 2002 12:18:32 -0000	1.1.2.3
  +++ guide-architecture.xml	22 May 2002 14:03:11 -0000	1.1.2.4
  @@ -3,9 +3,7 @@
   <document>
     <header>
       <title>Guide - Architectural overview</title>
  -
  -      <author name="Leo Simons" email="leosimons@apache.org"/>
  -
  +    <author name="Leo Simons" email="leosimons@apache.org"/>
     </header>
     <body>
       <section name="Introduction">
  @@ -17,10 +15,8 @@
         <p>
           Phoenix hosts one or more server applications at the same time in the same Virtual machine.
         </p>
  -      <figure>
  -        <title>Phoenix layer diagram</title>
  -        <graphic srccredit="Paul Hammant, 2001" fileref="images/phoenix-layers.jpg" format="JPEG"/>
  -      </figure>
  +        <center><b>Phoenix layer diagram</b></center>
  +        <center><img src="./images/phoenix-layers.jpg"/></center>
         <p>
           Shown above are three hosted server applications.  A mail server that would implement
           multiple listeners for incoming and outgoing services (POP3, SMTP, IMAP etc).  Outlook,
  @@ -42,10 +38,8 @@
             to function correctly.  The blocks are tied together with Assembly instructions and Configured
             externally.
           </p>
  -        <figure>
  -          <title>Phoenix application in block view</title>
  -          <graphic srccredit="Paul Hammant, 2001" fileref="images/phoenix-app-block.jpg" format="JPEG"/>
  -        </figure>
  +          <center><b>Phoenix application in block view</b></center>
  +          <center><img src="./images/phoenix-app-block.jpg"/></center>
         </subsection>
         <subsection name="Packaging in terms of block jar files">
           <p>
  @@ -56,7 +50,7 @@
           </p>
           <figure>
             <title>Phoenix application in block jar view</title>
  -          <graphic srccredit="Paul Hammant, 2001" fileref="images/phoenix-app-blockjars.jpg" format="JPEG"/>
  +          <center><img src="./images/phoenix-app-blockjars.jpg"/></center>
           </figure>
         </subsection>
         <subsection name="FtpServer as a Phoenix application">
  @@ -64,10 +58,8 @@
           FtpServer (part of the Avalon/Cornerstone project) is distributed in sar form.  Here is a
           view of it's blocks.  It has no third party jars that it depends on.
         </p>
  -        <figure>
  -          <title>FtpServer, a real Phoenix application</title>
  -          <graphic srccredit="Paul Hammant, 2001" fileref="images/phoenix-app-ftpserver.jpg" format="JPEG"/>
  -        </figure>
  +          <center><b>FtpServer, a real Phoenix application</b></center>
  +          <center><img src="./images/phoenix-app-ftpserver.jpg"/></center>
         </subsection>
         <p>
           Notes - Phoenix does not limit the number of blocks that it allows in a sar file.  We have taksdefs for Apache's Ant
  
  
  

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>