Changes between Version 1 and Version 2 of HowTos/HowToUseContentCaching

Timestamp:

02/14/10 05:59:23 (16 years ago)

Author:

boomfish (IP: 174.96.5.149)

Comment:

Changed spelling of 'adaptor' to 'adapter' so as to match the code.

HowTos/HowToUseContentCaching

@@ -48 +48 @@
 The cacheTimeout argument sets how long the cached event-handler or included view remains in the cache.  By default this is 5 seconds.  You can override this value using the defaultCacheTimeout as documented earlier in this document.  Or, you can use the cacheTimeout argument on an event-handler or include tag to control how long this item is cached.
 
-== The Beans Scope and the !CacheAdaptor ==
+== The Beans Scope and the !CacheAdapter ==
 
-Model-Glue uses a component known as a !CacheAdaptor to cache data.  The !CacheAdaptor is placed in the beans scope for all Controllers and is easily accessible there.  As an example, to dump this object you could ad this code within a controller:
+Model-Glue uses a component known as a !CacheAdapter to cache data.  The !CacheAdapter is placed in the beans scope for all Controllers and is easily accessible there.  As an example, to dump this object you could ad this code within a controller:
 {{{
-<cfdump var="#beans.CacheAdaptor#" />
+<cfdump var="#beans.CacheAdapter#" />
 }}}
-This object provides functions you can use to interact with the !CacheAdaptor.  You can, for example, purge the cache, add values, etc.  In fact, the legacy !AddToCache, !ExistsInCache, !GetFromCache,  and !RemoveFromCache functions on the controller simply access the beans-scoped !CacheAdaptor.
+This object provides functions you can use to interact with the !CacheAdapter.  You can, for example, purge the cache, add values, etc.  In fact, the legacy !AddToCache, !ExistsInCache, !GetFromCache,  and !RemoveFromCache functions on the controller simply access the beans-scoped !CacheAdapter.
 
-For complete details on the functions on the !CacheAdaptor see the API documentation.
+For complete details on the functions on the !CacheAdapter see the API documentation.
 == Creating Custom Caching Systems ==
 
 Model-Glue's built in caching system is intentionally simple.  It simply puts items into a component in the application scope.  If you need something more complex you can implement your own caching system.
 
-By creating your own !CacheAdaptor you could, for example, make use of Memcached or JDBM for an enterprise class caching system.
+By creating your own !CacheAdapter you could, for example, make use of Memcached or JDBM for an enterprise class caching system.
 
-To do this, you will need to create your own !CacheAdaptor by either extending the
+To do this, you will need to create your own !CacheAdapter by either extending the
 !ModelGlue.gesture.externaladapters.contentcaching.!SimpleTimedCache or simply implement the !ModelGlue.gesture.externaladapters.contentcaching.!IContentCache interface.
 
-Once you've created your cache adaptor you simply need to write it in.  To do so you will need to add a !ColdSpring bean in your !ColdSpring configuration file with an ID of "modelglue.cacheAdapter".  Here's a basic example:
+Once you've created your cache adapter you simply need to write it in.  To do so you will need to add a !ColdSpring bean in your !ColdSpring configuration file with an ID of "modelglue.cacheAdapter".  Here's a basic example:
 {{{
-<bean id="modelGlue.cacheAdapter" class="Model.cache.ExampleCacheAdaptor">
+<bean id="modelGlue.cacheAdapter" class="Model.cache.ExampleCacheAdapter">
   <!-- my configuration properties would go here -->
 </bean>
 }}}
-When you restart your Model-Glue application it will start using your new, custom, !CacheAdaptor.
+When you restart your Model-Glue application it will start using your new, custom, !CacheAdapter.