Gld Development: Difference between revisions
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 17: | Line 17: | ||
=Core Development= | =Core Development= | ||
{{Internal|gld Core Development#Overview|gld Core Development}} | |||
=Extension Development= | =Extension Development= | ||
| Line 30: | Line 24: | ||
:[[gld Extension Development]] | :[[gld Extension Development]] | ||
</blockquote> | </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.