...
The only supplied implementation is a wrapper around a <StorageService> plugin. It also includes an optimization for in-memory use that reduces the XML round tripping required, so binding it to an in-memory StorageService is not strictly necessary if the intent is to leave the data stored in memory.
When omitted, the optimized in-memory version with default settings will be used.
Reference
Attributes
Name | Type | Default | Description |
|---|
artifactTTL artifactTTL | time in seconds | 180 | Time-to-live for artifact mappings, to limit the risk of artifact theft and misuse. After the elapsed time, mappings become invalid. |
StorageService StorageService | XML IDRef | internal optimized | Optional reference to |
id attribute the id attribute of a previously |
defined <StorageService |
> element |
context context | string | When bound to a StorageService, an optional value can be supplied to isolate artifact mappings under a specific "context" key. Only needed if multiple deployments are sharing a single storage database. |
Example
Assuming a clustered deployment using an alternative <StorageService> element previously defined with an id of "MyMemcache":
...