Nscache - Revision history

Majidkhan59 at 10:33, 20 April 2010

2010-04-20T10:33:36Z

Akhassin at 04:17, 27 October 2009

2009-10-27T04:17:58Z

Akhassin at 02:47, 25 October 2009

2009-10-25T02:47:03Z

Akhassin at 02:24, 25 October 2009

2009-10-25T02:24:20Z

Gustafn at 19:02, 7 February 2009

2009-02-07T19:02:54Z

Gustafn at 18:56, 7 February 2009

2009-02-07T18:56:16Z

Gustafn at 18:55, 7 February 2009

2009-02-07T18:55:42Z

Gustafn at 00:04, 3 February 2009

2009-02-03T00:04:59Z

Gustafn at 00:04, 3 February 2009

2009-02-03T00:04:30Z

Gustafn at 00:03, 3 February 2009

2009-02-03T00:03:33Z

@@ Line 1: / Line 1: @@
 Tcl interface to AOLserver's caching API, by [[Rob Mayoff]].
-This module lives in AOLserver CVS[http://cvs.sourceforge.net/viewcvs.py/aolserver/nscache/]
+This module lives in AOLserver CVS[http://aolserver.cvs.sourceforge.net/viewvc/aolserver/nscache/]
 [[AOLserver]] implements a [[C API]] for caching arbitrary data. This module

@@ Line 7: / Line 7: @@
 with AOLserver 3.x using nsd8x, or AOLserver 4.x.
-'''In AOLserver 4.5.1 there is a builtin [[ns_cache]] command with largely equivalent but not identical functionality. Most noteably only serverwide caches are supported.''' It is possible to run this module in AOLserver 4.5.1, in which case it will override the builtin command.  Note, however, that in AOLserver 4.5.1 connection thread pools are not specific to a virtual server by default, so any -thread caches you create will be visible to all virtual servers using the same connection thread pool.
+'''In AOLserver 4.5.1 there is a builtin [[ns_cache]] command with largely equivalent but not identical functionality. Most noteably only serverwide caches are supported and expiration is no longer a sliding window from last access.''' It is possible to run this module in AOLserver 4.5.1, in which case it will override the builtin command.  Note, however, that in AOLserver 4.5.1 connection thread pools are not specific to a virtual server by default, so any -thread caches you create will be visible to all virtual servers using the same connection thread pool.
 Cache Types
@@ Line 39: / Line 39: @@
 The cache has a maximum size specified when the cache is created. The size of the cache is the sum of the sizes of all the values in the cache; keys do not count toward a cache's size. If inserting a value into the cache makes the cache's size exceed its maximum, then cache entries are evicted starting with the least-recently used entry until the size is below the maximum size (or until only the new value remains in the cache).
-Caches created with "-serverwide" option are common to all virtual servers in the process, whereas caches created without this option are attached to the current virtual server.
+Caches created with "-serverwide" option are common to all virtual servers in the process, whereas caches created without this option are attached to the current virtual server.  Note that non-serverwide caches are visible to [[ns_cache_stats]], etc commands built into AOLserver on all virtual servers.  Creating a same-name cache in multiple virtual servers will result in a warning in the server log but their contents will be separate.  What will happen if expiration/size settings are different?
 ----
@@ Line 52: / Line 52: @@
 Cache values are stored as counted strings, as in a global size-limited cache.
-The cache has a maximum entry lifetime, called its timeout, specified (in seconds) when the cache is created. Every timeout seconds, AOLserver flushes all cache entries that have not were not created or accessed in the last timeout seconds.
+The cache has an inactive timeout for entries, specified (in seconds) when the cache is created. Every timeout seconds, AOLserver flushes all cache entries that have not were not created or accessed in the last timeout seconds.  Note that the purpose here is to purge from memory entries that aren't being used, not to provide a strict expiration such as exists in ns_adp_include -cache, for example.
 Caches created with "-serverwide" option are common to all virtual servers in the process, whereas caches created without this option are attached to the current virtual server.  Note that non-serverwide caches are visible to [[ns_cache_stats]], etc commands built into AOLserver on all virtual servers.  Creating a same-name cache in multiple virtual servers will result in a warning in the server log but their contents will be separate.  What will happen if expiration/size settings are different?

@@ Line 15: / Line 15: @@
 Cache Commands
-* ns_cache create cachename ?-size maxsize? ?-timeout timeout? ?-thread boolean | -serverwide boolean?
+* ns_cache create cachename ?-size maxsize | -timeout timeout? ?-thread boolean | -serverwide boolean?
 * ns_cache eval cachename key script
 * ns_cache flush cachename key
@@ Line 69: / Line 69: @@
 Thread-private caches may offer higher performance if the cached values are complex objects such as lists or scripts, but require more storage than global caches.
 '''Cache Commands'''

@@ Line 5: / Line 5: @@
 [[AOLserver]] implements a [[C API]] for caching arbitrary data. This module
 provides a Tcl API on top of the [[C API]]. The module is only compatible
-with AOLserver 3.x using nsd8x, or AOLserver 4.x. '''In AOLserver 4.5.1 the module is not needed anymore and is replaced by the builtin [[ns_cache]] command.'''
+with AOLserver 3.x using nsd8x, or AOLserver 4.x.
 Cache Types
@@ Line 46: / Line 48: @@
   ns_cache create cachename -timeout timeout -serverwide 1
-Entries in a cache of this type are accessible to all threads. Each cache has its own mutex that protects access to its entries.
+Entries in a cache of this type are accessible to all threads. Each cache has its own SINGLE mutex that protects access to ALL its entries.
 Cache values are stored as counted strings, as in a global size-limited cache.
@@ Line 52: / Line 54: @@
 The cache has a maximum entry lifetime, called its timeout, specified (in seconds) when the cache is created. Every timeout seconds, AOLserver flushes all cache entries that have not were not created or accessed in the last timeout seconds.
-Caches created with "-serverwide" option are common to all virtual servers in the process, whereas caches created without this option are attached to the current virtual server.
+Caches created with "-serverwide" option are common to all virtual servers in the process, whereas caches created without this option are attached to the current virtual server.  Note that non-serverwide caches are visible to [[ns_cache_stats]], etc commands built into AOLserver on all virtual servers.  Creating a same-name cache in multiple virtual servers will result in a warning in the server log but their contents will be separate.  What will happen if expiration/size settings are different?
 ----
@@ Line 92: / Line 94: @@
 If script raises an error, or exits with break or continue, then ns_cache eval simply returns the same condition without modifying the cache.
 This command is particularly useful for global caches because of its atomicity. Consider this definition:

← Older revision		Revision as of 19:02, 7 February 2009
Line 139:		Line 139:
	ns_param nscache nscache.so		ns_param nscache nscache.so

−	[[Category Documentation]]	+	[[Category:Documentation]]

← Older revision		Revision as of 18:56, 7 February 2009
Line 139:		Line 139:
	ns_param nscache nscache.so		ns_param nscache nscache.so

−	[[Category Documentation~~]] - [[Category Core Tcl API~~]]	+	[[Category Documentation]]

← Older revision		Revision as of 18:55, 7 February 2009
Line 138:		Line 138:
	ns_section ns/server/YourServerName		ns_section ns/server/YourServerName
	ns_param nscache nscache.so		ns_param nscache nscache.so
		+
		+	[[Category Documentation]] - [[Category Core Tcl API]]