Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Technical Debt - Cleaning up Communication flow of Agent and Processor #50

Closed
JoshuaSBrown opened this issue Oct 25, 2022 · 2 comments
Closed
Labels
Priority: Medium Indicate the relative priority of the task to the project objectives as medium.

Comments

@JoshuaSBrown
Copy link
Collaborator

JoshuaSBrown commented Oct 25, 2022

In the ideal design, there would be two threads the processor thread and the agent thread, the agent would be the only thread that sends messages to the queue. The processor thread on the other hand would listen for new activities on the queue and execute them, any communication that needs to be sent back to the queue should require the processor thread hand off the communication to the agent thread.

Agent thread - sends to queue
Processor thread - receives from queue and executes activities

A refactor of the code is needed to implement this distinction.

@JoshuaSBrown JoshuaSBrown added the Priority: Medium Indicate the relative priority of the task to the project objectives as medium. label Nov 10, 2022
@rafaelfsilva
Copy link
Member

@JoshuaSBrown, is this implemented already? It looks like the separation related to the executor solves this issue?

@JoshuaSBrown
Copy link
Collaborator Author

Yes, this can be closed. #86

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Medium Indicate the relative priority of the task to the project objectives as medium.
Projects
None yet
Development

No branches or pull requests

2 participants