-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add Support for QWATCH Command with HTTP #553
Comments
@pratikpandey21 would like to work on this. |
lucifercr07
added a commit
to lucifercr07/dice
that referenced
this issue
Sep 18, 2024
lucifercr07
added a commit
to lucifercr07/dice
that referenced
this issue
Sep 20, 2024
lucifercr07
added a commit
to lucifercr07/dice
that referenced
this issue
Sep 20, 2024
lucifercr07
added a commit
to lucifercr07/dice
that referenced
this issue
Sep 20, 2024
lucifercr07
added a commit
to lucifercr07/dice
that referenced
this issue
Sep 20, 2024
lucifercr07
added a commit
that referenced
this issue
Sep 25, 2024
Closing, merged as part of #614 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Implement support for the QWATCH command over HTTP, utilizing Server-Sent Events (SSE) to enable real-time updates to clients based on changes to underlying data. This enhancement will allow HTTP clients to subscribe to SQL-like queries over data structures and receive push notifications whenever the results of the query change, providing a more efficient alternative to polling for updates.
Command Overview:
Command: QWATCH
HTTP Method: POST
Endpoint: /QWATCH
Body: SQL Query. Check here for Query reference.
Behaviour with HTTP:
Subscription Mechanism:
Response Format:
The server responds with an HTTP 200 OK status and sets the Content-Type header to text/event-stream.
Each update is sent as an SSE event with the following format:
data: [{"key": "<key>", "value": <JSON value>}]
Tasks:
The text was updated successfully, but these errors were encountered: