Base class for cache management

Testcases:

No testcase defined.

Partitioned cache, where the partition numbers are computed via a hash function. Key-partitioning is based on a modulo function using a special partition_key, which has to be numeric

Testcases:

No testcase defined.

Partitioned cache, where the partition numbers are computed via a modulo function from the numeric keys.

Testcases:

No testcase defined.

Lockfree caches are provided either as per-thread caches or per-request caches, sharing the property that accessing these values does not require locks. Typical applications of these caches are the per_request_cache and per_thread_cache.

See Also:

• Object ::acs::per_request_cache
• Object ::acs::per_thread_cache

Testcases:

No testcase defined.

Partitioned cache infrastructure. Partition numbers are computed via a modulo function from the numeric keys.

Testcases:

No testcase defined.

• ::acs::group_cache set -partition_key /integer/ /key/ /value/
• ::acs::group_cache flush_pattern -partition_key /integer/ /pattern/
• ::acs::group_cache init
• ::acs::group_cache show_all
• ::acs::group_cache flush_all ?-partition_key /value/?
• ::acs::group_cache eval ?-partition_key /value/? ?-expires /value/? ?-timeout /value/? ?-per_request? /key/ /command/
• ::acs::group_cache get ?-partition_key /value/? /key/
• ::acs::group_cache flush ?-partition_key /value/? /key/
• ::acs::group_cache flush_cache ?-partition_key /value/?

Testcases:

No testcase defined.

Generic cache. This cache is a successor of the util_memoize_cache, but in a partitioned fashion to make it scalable. It should only be used for situation, where no wild-card flushes are required.

• ::acs::misc_cache set -partition_key /value/ /key/ /value/
• ::acs::misc_cache flush_pattern -partition_key /value/ /pattern/
• ::acs::misc_cache init
• ::acs::misc_cache show_all
• ::acs::misc_cache flush_all ?-partition_key /value/?
• ::acs::misc_cache eval ?-partition_key /value/? ?-expires /value/? ?-timeout /value/? ?-per_request? /key/ /command/
• ::acs::misc_cache get ?-partition_key /value/? /key/
• ::acs::misc_cache flush ?-partition_key /value/? /key/
• ::acs::misc_cache flush_cache ?-partition_key /value/?

Testcases:

No testcase defined.

Lockfree cache with per-request live time of the entries. The purpose of the per-request cache is to cache computation results of a single request. The entries of this cache are therefore very short-lived. Some values are needed multiple times per request, and/or they should show consistently the same value during the same request, no matter, if concurrently, a value is changed (e.g. permissions). The per-request cache uses a Tcl variable in the global Tcl namespace, such it will be automatically reclaimed after the request. The per-request cache uses the prefix "::__acs_cache".

• ::acs::per_request_cache get -key /value/ /var/
• ::acs::per_request_cache eval -key /value/ ?-no_cache /value/? ?-no_empty? ?-from_cache_indicator /value/? /cmd/
• ::acs::per_request_cache flush ?-pattern /value/?

Testcases:

No testcase defined.

Lockfree cache with per-thread live time of the entries. The per-thread caches use namespaced variables, which are not touched by the automatic per-request cleanup routines of the server. So, the values cached in one requests can be used by some later request in the same thread. The entries are kept in per-thread caches as long as the thread lives, there is so far no automatic mechanism to flush these. So, per-thread caches are typically used for values fetched from the database, which do not change, unless the server is restarted. Note: the usage of per-thread caches is only recommended for static values, which do no change during the life time of the server, since there is so far no automatic measure in place to the flush values in every thread.

• ::acs::per_thread_cache get -key /value/ /var/
• ::acs::per_thread_cache eval -key /value/ ?-no_cache /value/? ?-no_empty? ?-from_cache_indicator /value/? /cmd/
• ::acs::per_thread_cache flush ?-pattern /value/?

Testcases:

No testcase defined.

Permission cache. This partitioned cache manages partition caching. In case of bottlenecks, increase the number of partitions and the cache size.

• ::acs::permission_cache set -partition_key /integer/ /key/ /value/
• ::acs::permission_cache flush_pattern -partition_key /integer/ /pattern/
• ::acs::permission_cache init
• ::acs::permission_cache show_all
• ::acs::permission_cache flush_all ?-partition_key /value/?
• ::acs::permission_cache eval ?-partition_key /value/? ?-expires /value/? ?-timeout /value/? ?-per_request? /key/ /command/
• ::acs::permission_cache get ?-partition_key /value/? /key/
• ::acs::permission_cache flush ?-partition_key /value/? /key/
• ::acs::permission_cache flush_cache ?-partition_key /value/?

Testcases:

No testcase defined.

Partitioned Cache for handling generic site node information. Site node caching is implemented using three different caches.

See Also:

• Object ::acs::site_nodes_id_cache
• Object ::acs::site_nodes_children_cache

• ::acs::site_nodes_cache set -partition_key /integer/ /key/ /value/
• ::acs::site_nodes_cache flush_pattern -partition_key /integer/ /pattern/
• ::acs::site_nodes_cache init
• ::acs::site_nodes_cache show_all
• ::acs::site_nodes_cache flush_all ?-partition_key /value/?
• ::acs::site_nodes_cache eval ?-partition_key /value/? ?-expires /value/? ?-timeout /value/? ?-per_request? /key/ /command/
• ::acs::site_nodes_cache get ?-partition_key /value/? /key/
• ::acs::site_nodes_cache flush ?-partition_key /value/? /key/
• ::acs::site_nodes_cache flush_cache ?-partition_key /value/?

Testcases:

No testcase defined.

Partitioned Cache for handling site node children. Site node caching is implemented using three different caches.

See Also:

• Object ::acs::site_nodes_cache
• Object ::acs::site_nodes_id_cache

• ::acs::site_nodes_children_cache set -partition_key /integer/ /key/ /value/
• ::acs::site_nodes_children_cache flush_pattern -partition_key /integer/ /pattern/
• ::acs::site_nodes_children_cache init
• ::acs::site_nodes_children_cache show_all
• ::acs::site_nodes_children_cache flush_all ?-partition_key /value/?
• ::acs::site_nodes_children_cache eval ?-partition_key /value/? ?-expires /value/? ?-timeout /value/? ?-per_request? /key/ /command/
• ::acs::site_nodes_children_cache get ?-partition_key /value/? /key/
• ::acs::site_nodes_children_cache flush ?-partition_key /value/? /key/
• ::acs::site_nodes_children_cache flush_cache ?-partition_key /value/?

Testcases:

No testcase defined.

Partitioned Cache for handling site node IDs. Site node caching is implemented using three different caches.

See Also:

• Object ::acs::site_nodes_cache
• Object ::acs::site_nodes_children_cache

• ::acs::site_nodes_id_cache set -partition_key /value/ /key/ /value/
• ::acs::site_nodes_id_cache flush_pattern -partition_key /value/ /pattern/
• ::acs::site_nodes_id_cache init
• ::acs::site_nodes_id_cache show_all
• ::acs::site_nodes_id_cache flush_all ?-partition_key /value/?
• ::acs::site_nodes_id_cache eval ?-partition_key /value/? ?-expires /value/? ?-timeout /value/? ?-per_request? /key/ /command/
• ::acs::site_nodes_id_cache get ?-partition_key /value/? /key/
• ::acs::site_nodes_id_cache flush ?-partition_key /value/? /key/
• ::acs::site_nodes_id_cache flush_cache ?-partition_key /value/?

Testcases:

No testcase defined.

XOTcl Object cache. This partitioned cache is used for objects with numeric keys based on the acs_object_ids of OpenACS. Most of these objects refer to content items or content revisions. In case of bottlenecks, increase the number of partitions and the cache size.

• ::xo::xotcl_object_cache init
• ::xo::xotcl_object_cache show_all
• ::xo::xotcl_object_cache flush_all ?-partition_key /value/?
• ::xo::xotcl_object_cache set ?-partition_key /value/? /key/ /value/
• ::xo::xotcl_object_cache flush_pattern ?-partition_key /value/? /pattern/
• ::xo::xotcl_object_cache eval ?-partition_key /value/? ?-expires /value/? ?-timeout /value/? ?-per_request? /key/ /command/
• ::xo::xotcl_object_cache get ?-partition_key /value/? /key/
• ::xo::xotcl_object_cache flush ?-partition_key /value/? /key/
• ::xo::xotcl_object_cache flush_cache ?-partition_key /value/?

Testcases:

No testcase defined.

XOTcl Object type cache. This partitioned cache is used for obtaining types for objects and for the lookup of item_ids via parent_id and name for the content repository. In case of bottlenecks, increase the number of partitions and the cache size.

• ::xo::xotcl_object_type_cache set -partition_key /integer/ /key/ /value/
• ::xo::xotcl_object_type_cache flush_pattern -partition_key /integer/ /pattern/
• ::xo::xotcl_object_type_cache init
• ::xo::xotcl_object_type_cache show_all
• ::xo::xotcl_object_type_cache flush_all ?-partition_key /value/?
• ::xo::xotcl_object_type_cache eval ?-partition_key /value/? ?-expires /value/? ?-timeout /value/? ?-per_request? /key/ /command/
• ::xo::xotcl_object_type_cache get ?-partition_key /value/? /key/
• ::xo::xotcl_object_type_cache flush ?-partition_key /value/? /key/
• ::xo::xotcl_object_type_cache flush_cache ?-partition_key /value/?

Testcases:

No testcase defined.

XOTcl Object package cache. This cache is used for package_ids of package names, for ids of root folders, and for certain properties of the database (has_ltree, has_hstore). In case of bottlenecks, increase the number of partitions and the cache size.

• ::xo::xotcl_package_cache show_all
• ::xo::xotcl_package_cache init
• ::xo::xotcl_package_cache set ?-partition_key /value/? /key/ /value/
• ::xo::xotcl_package_cache flush_pattern ?-partition_key /value/? /pattern/
• ::xo::xotcl_package_cache eval ?-partition_key /value/? ?-expires /value/? ?-timeout /value/? ?-per_request? /key/ /command/
• ::xo::xotcl_package_cache get ?-partition_key /value/? /key/
• ::xo::xotcl_package_cache flush ?-partition_key /value/? /key/
• ::xo::xotcl_package_cache flush_all
• ::xo::xotcl_package_cache flush_cache ?-partition_key /value/?

Testcases:

No testcase defined.

Xowiki cache. This partitioned cache is used for various caching purposes for xowiki. It is used for example for caching includlets (when requested), or for full file names of xowiki::File objects. In case of bottlenecks, increase the number of partitions and the cache size.

• ::xowiki::cache set -partition_key /integer/ /key/ /value/
• ::xowiki::cache flush_pattern -partition_key /integer/ /pattern/
• ::xowiki::cache init
• ::xowiki::cache show_all
• ::xowiki::cache flush_all ?-partition_key /value/?
• ::xowiki::cache eval ?-partition_key /value/? ?-expires /value/? ?-timeout /value/? ?-per_request? /key/ /command/
• ::xowiki::cache get ?-partition_key /value/? /key/
• ::xowiki::cache flush ?-partition_key /value/? /key/
• ::xowiki::cache flush_cache ?-partition_key /value/?

Testcases:

No testcase defined.

Flush a single entry in the cache

Switches:

-partition_key (optional)

Parameters:

key (required)

Testcases:

No testcase defined.

Flush all contents of all (partitioned) caches. In the case of a base ::acs::Cache, it is identical to "flush_cash".

Testcases:

No testcase defined.

Flush all entries in a cache.

Switches:

-partition_key (optional)

Testcases:

No testcase defined.

Flush in the cache a value based on a pattern operation. Use this function rarely, since on large caches (e.g. 100k entries or more) the glob operation will cause long locks, which should be avoided. The partitioned variants can help to reduce the lock times.

Switches:

-partition_key (optional)

Parameters:

pattern (required)

Testcases:

No testcase defined.

The "get" method retrieves data from the cache. It should not be used for new applications due to likely race conditions, but legacy applications use this. As implementation, we use the AOLserver API emulation.

Switches:

-partition_key (optional)

Parameters:

key (required)

Testcases:

No testcase defined.

If the name was not provided, use the object name as default.

Testcases:

No testcase defined.

Set a single value in the cache. This code uses ns_cache_eval to achieve this behavior, which is typically an AOLserver idiom and should be avoided.

Switches:

-partition_key (optional)

Parameters:

key (required)

value (required)

Testcases:

No testcase defined.

Log all cache keys to the system log. The primary usage is for debugging.

Testcases:

No testcase defined.

flush just in all partitions

Switches:

-partition_key (required)

Parameters:

pattern (required)

Testcases:

No testcase defined.

Set a single value in the cache. It transforms the partition key into a hash value. This code uses ns_cache_eval to achieve this behavior, which is typically an AOLserver idiom and should be avoided.

Switches:

-partition_key (required)

Parameters:

key (required)

value (required)

Testcases:

No testcase defined.

Flush just in the determined partition

Switches:

-partition_key (required, integer)

Parameters:

pattern (required)

Testcases:

No testcase defined.

Set a single value in the cache. This code uses ns_cache_eval to achieve this behavior, which is typically an AOLserver idiom and should be avoided.

Switches:

-partition_key (required, integer)

Parameters:

key (required)

value (required)

Testcases:

No testcase defined.

Use the "prefix" to determine whether the cache is per-thread or per-request.

Switches:

-key (required)

key for caching, should start with package-key and a dot to avoid name clashes

-no_cache (optional)

list of returned values that should not be cached

-no_empty (optional, defaults to "false")

don't cache empty values. This flag is deprecated, one should use the no_cache flag instead.

-from_cache_indicator (optional)

variable name to indicate whether the returned value was from cache or not

Parameters:

cmd (required)

command to be executed.

Returns:

return the last value set (don't use "return").

Testcases:

No testcase defined.

Flush a cache entry based on the pattern (which might be wild-card-free). Currently, the clusterwide flushing is omitted. We have the per-request cache (clusterwide operations do not make sense for this) and per-thread caching. The per-thread caching application have to be aware that flushing is happening only in one thread, so clusterwide operations will only start to make sense, when the all threads of a server would be cleaned.

Switches:

-pattern (optional, defaults to "*")

Testcases:

No testcase defined.

Get entry with the provided key from this cache if it exists. In most cases, the "eval" method should be used.

Switches:

-key (required)

cache key

Parameters:

var (required)

Returns:

return boolean value indicating success.

Testcases:

No testcase defined.

Flush all entries in all partitions of a cache.

Switches:

-partition_key (optional)

Testcases:

No testcase defined.

If the name was not provided, use the object name as default for the cache name.

Testcases:

No testcase defined.

Log all cache keys of all partitions to the system log. The primary usage is for debugging.

Testcases:

No testcase defined.

Evaluate an expression. When the acs-tcl.DiskCache parameter is set, cache the result on the disk. If a cache already exists, return the cached value.

Switches:

-call (required)

a Tcl snippet executed in the caller scope.

-key (required)

a key used to name the directory where the disk cache will be stored.

-id (required)

an id used to name the file where the disk cache will be stored. The name will also depend on a hash of the actual snippet.

Partial Call Graph (max 5 caller/called nodes):

Testcases:

disk_cache

Flushes the filesystem cache.

Switches:

-key (required)

the key used to name the directory where the disk cache is stored.

-id (required)

the id used to name the file where the disk cache is stored.

See Also:

• acs::disk_cache_eval

Partial Call Graph (max 5 caller/called nodes):

Testcases:

disk_cache