The global PYPCK_TASKS functionality is factored out into TaskRegistry class. Each PchkConnection gets it's own separate registry. This registry is used for creating all tasks in connection, module, and request_handler modules. So it's now possible to have multiple distinct PchkConnection objects in the same task.
First draft of what the local TaskRegistry could look like. Tests for multiple connections in on process are still TODO.
@alengwenus Please let me know what think about the approach.
The global PYPCK_TASKS functionality is factored out into TaskRegistry class. Each PchkConnection gets it's own separate registry. This registry is used for creating all tasks in connection, module, and request_handler modules. So it's now possible to have multiple distinct PchkConnection objects in the same task.
First draft of what the local TaskRegistry could look like. Tests for multiple connections in on process are still TODO.
@alengwenus Please let me know what think about the approach.