Show
Ignore:
Timestamp:
09/27/08 16:00:05 (3 months ago)
Author:
mikeseth
Message:

little cleanup, wording improvement

Files:
1 modified

Legend:

Unmodified
Added
Removed

  • documentation/trunk/topics/agavi-services.dita

    r2747 r2949  
    1717  the "context" of the application. This envelope is exposed to 
    1818  your application as the global singleton <apiname>Context</apiname> object.</p> 
    19       <p>The Context object is available to all of your code. You use 
    20   the Context object to access the global framework services. For 
    21   example, if you want to retrieve a named database connection 
    22   from Agavi <apiname>DatabaseManager</apiname>, you'll do approximately the following:</p> 
    23       <codeblock class="php" conref="examples.xml#services-example-context"/> 
     19      <p>The Context object is available to all of your code. It is an 
     20  important object, since you use it to access 
     21  the global services of the framework. For example, if you wanted to 
     22  retrieve a named database connection from 
     23  Agavi <apiname>DatabaseManager</apiname>, you'd do 
     24  it like this:</p> <codeblock class="php" 
     25  conref="examples.xml#services-example-context"/> 
    2426    </section> 
    2527    <section> 
    2628      <title>Application configuration</title> 
    27       <p>Agavi configuration system is a general purpose service is 
     29      <p>Agavi configuration system stores names and their 
     30  corresponding values. It is a general purpose service that's 
    2831  used both by Agavi applications and the framework itself. The 
    2932  configuration system compiles XML configuration files into 
    30   executable PHP code. Here's some example code: 
     33  executable PHP code. Agavi defines some configuration files 
     34  for its own purposes. Here's some example code: 
    3135      </p> 
    3236      <codeblock class="php" conref="examples.xml#services-example-config"/> 
    … …  
    8387      code makes.</p> 
    8488      <p>On the application level, Agavi provides a security mechanism 
    85       that distinguishes between users and between permissions, 
    86       opening a clear way to specify who is allowed to access what in 
    87       your application. Access security is enforced on the framework 
    88       level as well.</p> 
     89      that understands individual user permissions, allowing to 
     90      specify who is allowed to access what in your 
     91      application. Access security is enforced on the framework level 
     92      as well.</p> 
    8993    </section> 
    9094    <section> 
    … …  
    99103      <p>Agavi also ships with a date manipulation library.</p> 
    100104    </section> 
    101     <section> 
    102       <title> 
    103       </title> 
    104     </section> 
    105105  </body> 
    106106</topic>