-
Notifications
You must be signed in to change notification settings - Fork 53
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
Delegate Communcation Streams #1025
Labels
Comments
Can you elaborate a bit on this part? maybe give an example scenario.
|
Another benefit is avoiding spam gateway logs from the delegate server:
|
Well, I suppose we could just remove that log statement 😛 |
kralicky
added
complexity/medium
priority/low
enhancement
New feature or request
labels
Jul 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add support for delegate stream communication. Currently only single messages and broadcasts are supported, but streams would be useful when the gateway needs to continuously check the agent for data with minimal network data.
For example, when monitoring the progress of a data import (as in #1014) we currently store the progress of targets on the agent and have to continuously poll the agent to keep the user up-to-date. But a stream would allow the agent to inform the gateway every time there is an update to the target status, which would remove the need for the gateway to check the agent for import status.
The text was updated successfully, but these errors were encountered: