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

Websocket notifications #40

Open
jan-dolejsi opened this issue Jun 1, 2022 · 0 comments
Open

Websocket notifications #40

jan-dolejsi opened this issue Jun 1, 2022 · 0 comments

Comments

@jan-dolejsi
Copy link

jan-dolejsi commented Jun 1, 2022

Instead of the periodic polling and better still than long-polling (where the client tells the server how long is it willing to wait till the connection times-out), websockets are the most economic mechanism for delivering notifications to the client:

Example implementation:
https://async-websockets.readthedocs.io/en/latest/

The client would establish a connection with the ws://server:port/check/qwer-qwer-qwer-wqre or ws://server:port/package/xyz/solve/qwer-qwer-qwer-wqre and the server would deliver notifications about new plans, or about the search status i.e. that the planner finished planning.

If the planner was capable of exposing more diagnostic information, it could also be sending the info about the states created and expanded in order to populate the diagnostic outputs like the visual search debugger in VS Code.

The client would also be able to send request to kill the search even before the timeout elapses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant