application should allow for the creation of multiple threads which execute code
Does different instances of the plugin initialise different processes of the interpreter?
How to handle shared resources, i.e. log files and databases?
-- Option: one file per process --> aggregate them later
-- Option: brainstorm way to invoke multiple instances and manage them by ourselves
- application should allow for the creation of multiple threads which execute code
- Does different instances of the plugin initialise different processes of the interpreter?
- How to handle shared resources, i.e. log files and databases?
- -- Option: one file per process --> aggregate them later
- -- Option: brainstorm way to invoke multiple instances and manage them by ourselves
foefl
added the question label 2025-03-28 11:07:35 +00:00
Currently multi-threading management is not desired because of the plugin architecture. Each plugin operates within another environment defined by the customer's application. Therefore, a generic architecture might be possible, but the common strategy is to let the customer implement multi-threading and handle multiple instances of the plugin.
Reopen the issue if a generic multi-threading solution becomes relevant
Currently multi-threading management is not desired because of the plugin architecture. Each plugin operates within another environment defined by the customer's application. Therefore, a generic architecture might be possible, but the common strategy is to let the customer implement multi-threading and handle multiple instances of the plugin.
**Reopen the issue if a generic multi-threading solution becomes relevant**
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently multi-threading management is not desired because of the plugin architecture. Each plugin operates within another environment defined by the customer's application. Therefore, a generic architecture might be possible, but the common strategy is to let the customer implement multi-threading and handle multiple instances of the plugin.
Reopen the issue if a generic multi-threading solution becomes relevant