|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||
See:
Description
| Interface Summary | |
|---|---|
| HierarchicalLockManager<K,M> | Interface to manage locks on hierarchically organized resources. |
| LockManager<K,M> | Main interface to acquire and manage locks. |
| Class Summary | |
|---|---|
| AbstractLockManager<K,M> | Abstract implementation of LockManager. |
| AbstractLockManager.KeyEntry<K,M> | |
| DefaultHierarchicalLockManager<M> | Default implementation of the HierarchicalLockManager. |
| RWLockManager<K,M> | Advanced read/write lock implementation of a LockManager based on
ResourceRWLock. |
| SimpleLockManager<K,M> | Default implementation of LockManager based on ReentrantLock. |
| Enum Summary | |
|---|---|
| LockException.Code | |
| Exception Summary | |
|---|---|
| LockException | Exception displaying a lock problem. |
Central package for locking related stuff. It contains interfaces and implementations to handle your locks in a transactional way. That means you divide your work in blocks and free all locks accumulated in that block at its very end. A common, shared timeout protects all locking requests.
The central interface is the one of the lock manager. It's recommended implementation is the read/write lock manager that features read/write locks and efficient deadlock detection.
If you have hierarchical resources to lock you can use the hierarchical lock manager interface with its default implementation.
If you need a custom implementation of a lock mamanger it is recommended to base your work on the on an abstract base.
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||