cvs commit: jakarta-slide/src/doc architecture.xml namespace.xml security.xml

[re...@apache.org]

remm        01/06/09 18:18:18

  Modified:    src/doc  architecture.xml namespace.xml security.xml
  Log:
  - Reuse diagrams from the J1 presentation in the website, are they are nicer
    and more up to date.
  
  Revision  Changes    Path
  1.4       +21 -1     jakarta-slide/src/doc/architecture.xml
  
  Index: architecture.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-slide/src/doc/architecture.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- architecture.xml	2000/07/18 22:44:56	1.3
  +++ architecture.xml	2001/06/10 01:18:17	1.4
  @@ -24,8 +24,28 @@
         the offered client API.
       </p>
       
  +  </section>
  +
  +  <section title="External Architecture">
  +
       <p>
  -      <img src="images/architecture.png"/>
  +      <img src="images/arch-ext.png"/>
  +    </p>
  +    
  +  </section>
  +
  +  <section title="Internal Architecture">
  +
  +    <p>
  +      <img src="images/arch-int1.png"/>
  +    </p>
  +    
  +  </section>
  +
  +  <section title="Transaction Management">
  +
  +    <p>
  +      <img src="images/arch-int2.png"/>
       </p>
       
     </section>
  
  
  
  1.5       +9 -11     jakarta-slide/src/doc/namespace.xml
  
  Index: namespace.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-slide/src/doc/namespace.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- namespace.xml	2000/07/20 00:10:23	1.4
  +++ namespace.xml	2001/06/10 01:18:17	1.5
  @@ -111,20 +111,18 @@
         automatically inherited by sub-nodes.  Here is an example of how one 
         namespace might be mapped into different services:
         
  -    <h3>Namespace mapping onto different Low-Level Services </h3>
  -    <img src="images/namespace.png"/>
  -  </p>
  +      <h3>Namespace mapping onto different Low-Level Services </h3>
  +      <img src="images/ns1.png"/>
  +    </p>
       
       <p>
  -      In this example, there are four different service mappings.  
  +      In this example, there are three different service mappings.  
         All <tt>actions</tt> are stored together, possibly in a memory store, 
  -      all <tt>files</tt> are stored in a specific store (possibly in a remote 
  -      FTP file server), while <tt>paul</tt>'s files could be stored on his 
  -      own computer.  The rest (<tt>/</tt>, <tt>/users</tt> and 
  -  <tt>/users/root</tt> in the example above) could be mapped into an 
  -  arbitrary SQL database.
  -</p>
  -</section>
  +      all <tt>files</tt> are stored in a specific store (here, the filesystem).
  +      The <tt>/users</tt> are mapped into a SQL database.
  +    </p>
  +  
  +  </section>
     
     </body>
   
  
  
  
  1.6       +4 -0      jakarta-slide/src/doc/security.xml
  
  Index: security.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-slide/src/doc/security.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- security.xml	2000/12/28 11:47:30	1.5
  +++ security.xml	2001/06/10 01:18:17	1.6
  @@ -44,6 +44,10 @@
       
       <section title="Principles">
   
  +        <p>
  +          <img src="images/ns2.png"/>
  +        </p>
  +
           <p>Every <tt>ObjectNode</tt> has associated permissions, which are tuples with the following format:
   <pre>
   (target subject,      executing subject,    action,            inheritance)