Important Terms
Important terms that are not defined elsewhere.
Last updated
Important terms that are not defined elsewhere.
Last updated
A Workers application is built up out of one or more Workers, connected together in a call-chain hierarchy that looks like a tree. Lets take an example of an application that is built out of four Workers, whose Worker call-chain hierarchy is represented by the diagram below.
Every Workers application has a Head Worker. An applications Head Worker is the Worker at the very top of an application's Worker call-chain hierarchy. In the figure below, Worker A is the Head Worker of the application.
A Caller is a Worker that calls (or loads) one or more Workers. In the figure below, Worker A is the Caller of Workers B, C and D.
A subWorker is a Worker that is called (or loaded) by another Worker. In the figure below, Worker B, Worker C and Worker D are subWorkers of Worker A.
A Worker's Main Data Wire is the Worker class wire that starts at the Worker's object constant and runs through the Worker's MHL. See the image below.
Worker handles are class wires that contain a Worker's Public Properties (such as the Worker's Message Queue). Worker handles are used to send messages to a specific Worker instance via the Worker's Public Request VIs. An example of a Worker's handle could be:
subWorker class wires that are used by a Caller's MHL (such as in the image above).
The Worker class wire that exits an Asynchronous Launcher VI.
The Worker class wire that exits a Dynamically Load Worker Public API VI.
