|
This implementation uses a synchronized hash map to store all configurations.
This is a bottleneck and may be a point of contention when many threads
required configurations simultaniously.
Configuration objects are cached lazily, i.e. they are cached after they
are requested the first time. Once a configuration object is cached, the
cache will listen for Node events on the configuration. If a node event
occurs, the entire cache is cleared. This is done to prevent inconsistencies
between this cache and caches internal to the configuration objects
themselves in the case of nested configurations.
Copyright 2002 Sapient
since: carbon 1.1 author: Douglas Voet, Oct 24, 2002 version: $Revision: 1.11 $($Author: dvoet $ / $Date: 2003/05/05 21:21:16 $) |