Gld Concepts: Difference between revisions
(→Store) |
No edit summary |
||
| Line 16: | Line 16: | ||
Store types: in-memory, hierarchical, etc. A fully qualified class name can also be specified - the corresponding key store will be instantiated if the implementation is found on the class path. Also see [[gld Configuration#Store_Configuration|store configuration]]. | Store types: in-memory, hierarchical, etc. A fully qualified class name can also be specified - the corresponding key store will be instantiated if the implementation is found on the class path. Also see [[gld Configuration#Store_Configuration|store configuration]]. | ||
=Extension= | |||
Example: <tt>jboss-datagrid-7.0.0.jar</tt>. | |||
The extension JAR name follows as close as possible the original product nomenclature and versioning scheme. | |||
<font color=red>Use the original distribution naming scheme.</font> | |||
Revision as of 23:11, 14 December 2016
Internal
Load Driver Instance
A load driver instance runs inside a Java virtual machine executing a control loop on the main thread.
Error Handling
The main LoadDriver loop is not supposed to throw any exception, all exception will be handled internally, and they will be logged at stderr or sent to the log file, depending on how the load driver logging is configured.
Store
The store is the ... used to save the key generated during a load run, so they can be accessed later. Most commonly, it is implemented as local file storage.
Store types: in-memory, hierarchical, etc. A fully qualified class name can also be specified - the corresponding key store will be instantiated if the implementation is found on the class path. Also see store configuration.
Extension
Example: jboss-datagrid-7.0.0.jar.
The extension JAR name follows as close as possible the original product nomenclature and versioning scheme.
Use the original distribution naming scheme.