Gld Development: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (15 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=Internal= | =Internal= | ||
* [[gld#Development|gld]] | * [[Generic Load Driver (gld)#Development|gld]] | ||
=GitHub= | =GitHub= | ||
| Line 9: | Line 9: | ||
</blockquote> | </blockquote> | ||
= | =Overview= | ||
From a project perspective, gld consists of a core and extensions. | |||
The core contains the load driver multi-threaded load engine, logic to coordinate multiple load driver instances and other logic required by the load driver. All these are packaged as gld-load-driver-*.jar. The load driver runtime is not aware of any specific load content generator, it only interacts with a generic set of interfaces, packaged as gld-api-*.jar. To develop a load content generator extension, appropriate for a specific use case, and with a specific set of concrete dependencies, the extension will only need to depend on gld-api. | |||
=Core Development= | |||
{{Internal|gld Core Development#Overview|gld Core Development}} | |||
=Extension Development= | |||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | |||
:[[gld Extension Development]] | |||
</blockquote> | |||
Latest revision as of 22:57, 5 September 2017
Internal
GitHub
Overview
From a project perspective, gld consists of a core and extensions.
The core contains the load driver multi-threaded load engine, logic to coordinate multiple load driver instances and other logic required by the load driver. All these are packaged as gld-load-driver-*.jar. The load driver runtime is not aware of any specific load content generator, it only interacts with a generic set of interfaces, packaged as gld-api-*.jar. To develop a load content generator extension, appropriate for a specific use case, and with a specific set of concrete dependencies, the extension will only need to depend on gld-api.