avalon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mcconn...@apache.org
Subject svn commit: rev 22700 - in avalon/trunk/central/site/src/xdocs/products/runtime: reference/component reference/component/artifacts reference/component/lifestyle system/meta/info/type/info system/meta/tags
Date Thu, 08 Jul 2004 09:37:22 GMT
Author: mcconnell
Date: Thu Jul  8 02:37:21 2004
New Revision: 22700

Modified:
   avalon/trunk/central/site/src/xdocs/products/runtime/reference/component/artifacts/manager.xml
   avalon/trunk/central/site/src/xdocs/products/runtime/reference/component/index.xml
   avalon/trunk/central/site/src/xdocs/products/runtime/reference/component/lifestyle/index.xml
   avalon/trunk/central/site/src/xdocs/products/runtime/system/meta/info/type/info/index.xml
   avalon/trunk/central/site/src/xdocs/products/runtime/system/meta/info/type/info/lifestyle.xml
   avalon/trunk/central/site/src/xdocs/products/runtime/system/meta/tags/type.xml
Log:
Remove references to unsupported pool lifestyle semantics.

Modified: avalon/trunk/central/site/src/xdocs/products/runtime/reference/component/artifacts/manager.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/products/runtime/reference/component/artifacts/manager.xml
(original)
+++ avalon/trunk/central/site/src/xdocs/products/runtime/reference/component/artifacts/manager.xml
Thu Jul  8 02:37:21 2004
@@ -66,9 +66,9 @@
 
       <subsection name="Lookup and Release Semantics">
         <p>
-Services are aquired by passing the dependency key under the lookup operation.  If no key
is declared, the component can aquire the service using the value of the type attribute. 
When a component no longer requires a service it can relase the service, thereby notifying
the container that the service instance is no longer required.   While release of a service
is optional, component authors shyould be aware that the component implementation underlying
the service may be pooled. As such, release of the service may have a direct impact on memory
consumption and overall performance.
+Services are aquired by passing the dependency key under the lookup operation.  If no key
is declared, the component can aquire the service using the value of the type attribute. 
When a component no longer requires a service it can relase the service, thereby notifying
the container that the service instance is no longer required.   While release of a service
is optional, component authors should be aware that the component implementation underlying
the service may be pooled. As such, release of the service may have a direct impact on memory
consumption and overall performance.
         </p>
-        <p><i>Example of an aquisition and relace cycle.</i></p>
+        <p><i>Example of an aquisition and release cycle.</i></p>
 <source>
    /**
     * Creation of a new instance during which a service is aquired,

Modified: avalon/trunk/central/site/src/xdocs/products/runtime/reference/component/index.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/products/runtime/reference/component/index.xml	(original)
+++ avalon/trunk/central/site/src/xdocs/products/runtime/reference/component/index.xml	Thu
Jul  8 02:37:21 2004
@@ -57,7 +57,7 @@
           <tr>
             <td><a href="lifestyle/index.html">Lifestyle</a></td>
             <td>
-A component implementation is associated with a particular lifestyle.  A lifestyle is policy
that deals with the decision to create a new component as opposed to to supplying a reference
to an existing component.  Examples of lifestyle policies include "singleton", "per-thread",
"pooled", and "transient".  This section of the specification describes each policy and the
related semantics that a component author can assume concerning instantiation and references
sharing. 
+A component implementation is associated with a particular lifestyle.  A lifestyle is policy
that deals with the decision to create a new component as opposed to to supplying a reference
to an existing component.  Examples of lifestyle policies include "singleton", "per-thread",
and "transient".  This section of the specification describes each policy and the related
semantics that a component author can assume concerning instantiation and references sharing.

             </td>
           </tr>
         </table>

Modified: avalon/trunk/central/site/src/xdocs/products/runtime/reference/component/lifestyle/index.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/products/runtime/reference/component/lifestyle/index.xml
(original)
+++ avalon/trunk/central/site/src/xdocs/products/runtime/reference/component/lifestyle/index.xml
Thu Jul  8 02:37:21 2004
@@ -42,10 +42,6 @@
         <td>A new instance of the component will be created relative to each distinct
thread.</td>
       </tr>
       <tr>
-        <td>pool</td>
-        <td>A container shall maintain a pool of components.</td>
-      </tr>
-      <tr>
         <td>transient</td>
         <td>New instance of the component are created on a per request basis.</td>
       </tr>

Modified: avalon/trunk/central/site/src/xdocs/products/runtime/system/meta/info/type/info/index.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/products/runtime/system/meta/info/type/info/index.xml
(original)
+++ avalon/trunk/central/site/src/xdocs/products/runtime/system/meta/info/type/info/index.xml
Thu Jul  8 02:37:21 2004
@@ -40,7 +40,7 @@
             <td><a href="lifestyle.html">lifestyle</a></td><td>0..1</td>
             <td>
              Declaration of the component lifestyle. May contain one of the 
-             recognized values "singleton", "thread", "pooled", or "transient".
+             recognized values "singleton", "thread", or "transient".
              If not supplied the default value is transient.
             </td>
           </tr>

Modified: avalon/trunk/central/site/src/xdocs/products/runtime/system/meta/info/type/info/lifestyle.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/products/runtime/system/meta/info/type/info/lifestyle.xml
(original)
+++ avalon/trunk/central/site/src/xdocs/products/runtime/system/meta/info/type/info/lifestyle.xml
Thu Jul  8 02:37:21 2004
@@ -14,7 +14,7 @@
       <subsection name="Description">
         <p>
         Declaration of the component lifestyle. May contain one of the 
-        recognized values "singleton", "thread", "pooled", or "transient".
+        recognized values "singleton", "thread", or "transient".
         If not supplied the default value is "transient".
         </p>
       </subsection>

Modified: avalon/trunk/central/site/src/xdocs/products/runtime/system/meta/tags/type.xml
==============================================================================
--- avalon/trunk/central/site/src/xdocs/products/runtime/system/meta/tags/type.xml	(original)
+++ avalon/trunk/central/site/src/xdocs/products/runtime/system/meta/tags/type.xml	Thu Jul
 8 02:37:21 2004
@@ -49,7 +49,6 @@
                 <li>singleton - an instance may be shared between 
                     multiple clients</li>
                 <li>thread - one instance per thread</li>
-                <li>pooled - each client has a unique instance managed by a pool</li>
                 <li>transient - new instance are created on demand</li>
               </ul>
             </td>

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org


Mime
View raw message