You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: rfcs/0014-task-workers.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,9 +30,11 @@ The pool should also be re-used when multiple projects are being built, either i
30
30
### Terminology
31
31
32
32
*`Worker`: A Node.js [Worker thread](https://nodejs.org/api/worker_threads.html) instance
33
-
*`Task Processor`: A module associated with a UI5 Tooling build task (standard or custom) that can be executed in a `Worker`
33
+
*`Build Task`: A UI5 Tooling build task such as "minify" or "buildThemes" (standard tasks) or any [custom task](https://sap.github.io/ui5-tooling/stable/pages/extensibility/CustomTasks/)
34
+
*`Task Processor`: A module associated with a UI5 Tooling Build Task (standard or custom) that can be executed in a `Worker`
35
+
*`Dispatch Broker`: A ui5-project module coupled to the lifecycle of a Graph Build (similar to the `ProjectBuildContext`). It forwards requests from Build Tasks
34
36
*`Thread Runner`: A ui5-project module that will be loaded in a `Worker`. It handles communication with the main thread and executes a `Task Processor` on request
35
-
*`Dispatcher`: A ui5-project singleton module which uses a library like [`workerpool`](https://github.com/josdejong/workerpool) to spawn and manage `Worker` instances in order to have them execute any `Task Processor` requested by the build task
37
+
*`Dispatcher`: A ui5-project singleton module which uses a library like [`workerpool`](https://github.com/josdejong/workerpool) to spawn and manage `Worker` instances in order to have them execute any `Task Processor` requested by the Build Task
36
38
- Handles the `Worker` lifecycle
37
39
38
40

@@ -58,7 +60,7 @@ The pool should also be re-used when multiple projects are being built, either i
58
60
59
61
Similar to Tasks, Task Processors shall be invoked with a well defined signature:
60
62
61
-
*`resources`: An array of `@ui5/fs/Resource` provided by the build task
63
+
*`resources`: An array of `@ui5/fs/Resource` provided by the Build Task
62
64
*`options`: An object provided by the build task
63
65
*`workspace`: Reader to read project files
64
66
*`dependencies`: Reader or collection to read dependency files
0 commit comments