bloritsch    2002/07/17 07:10:03

  Modified:    fortress/src/xdocs book.xml
  Added:       fortress/src/xdocs features.xml
  Log:
  Add new features doc so that we can see what sets Fortress apart
  
  Revision  Changes    Path
  1.5       +1 -0      jakarta-avalon-excalibur/fortress/src/xdocs/book.xml
  
  Index: book.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon-excalibur/fortress/src/xdocs/book.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- book.xml  12 Jul 2002 15:56:07 -0000      1.4
  +++ book.xml  17 Jul 2002 14:10:03 -0000      1.5
  @@ -15,6 +15,7 @@
        
     <menu label="Essentials">
       <menu-item label="Overview" href="index.html"/>
  +    <menu-item label="Features" href="features.html"/>
       <menu-item type="external" id="download" label="Download" 
href="http://jakarta.apache.org/builds/jakarta-avalon-excalibur/release"/>
       <menu-item type="external" id="api-docs" label="API Docs" href="api/"/>
   
  
  
  
  1.1                  jakarta-avalon-excalibur/fortress/src/xdocs/features.xml
  
  Index: features.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
  
  <document>
    <header>
      <title>Excalibur Fortress - Features</title>
      <authors>
        <person name="Berin Loritsch" email="[EMAIL PROTECTED]"/>
      </authors>
    </header>
    <body>
      <s1 title="Features">
        <p>
        Fortress provides a framework for you to easily create your
        own application specific containers.  We strive to make it
        easy for you to do without sacrificing any power.  Fortress
        allows you to focus on the core issues in your system, without
        worrying about the component management getting in your way.
        </p>
        <s2 title="Asynchronous Component Management">
        <p>
            Most component management functions don't take that long to
          perform, but the time they do take can directly affect how
          many requests your system can process at the same time.  For
          that reason, we use the CommandManager from the Event package
          to manage our components.  By moving all the management
          functions to a limited number of background threads, we are
          able to save you time in the critical processing path.
          </p>
        <p>
            The CommandManager can be extended to your components as well.
          That way, your components can perform management tasks in the
          background as well.  Fortress will likely be your choice of
          containers if you have strict performance constraints.
          </p>
        </s2>
        <s2 title="Extensible Lifecycle">
        <p>
            Fortress has support for an experimental feature that allows
          you to extend your component lifecycle in an application
          specific manner.  If it proves to be a truly useful feature,
          other Avalon containers will adopt it.
          </p>
        </s2>
        <s2 title="Instrumentation">
          <p>
            Fortress is integrated with the Instrumentation package so
          you can get a graphical view of the health of your system
          at runtime.  We integrate sampling points for each of the
          component handlers so that you can see how many component
          instances each handler is responsible for.  Using that
          information, you can tune your container more intelligently.
          </p>
        </s2>
      </s1>
    </body>
    <footer>
      <legal>
        Copyright (c) @year@ The Jakarta Apache Project All rights reserved.
        $Revision: 1.1 $ $Date: 2002/07/17 14:10:03 $
      </legal>
    </footer>
  </document>
  
  
  

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to