We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
after the authentication to done on ui-control, for each query request. #81 #77 #85
We then implement authenticated subscription upon Event Arrival.
The text was updated successfully, but these errors were encountered:
Revisiting the Apollo documentation, it recommends to use subscription (websocket), for low-latency requirement.
BTW, the current requirement will get notification, after commit is made successfully. And, it is better to use long-poll.
Therefore, I make use of Redis, to store the event arrival information, with redis keys to starting with "noti::"
The UI-control, will use periodically poll to obtain this notification information from Redis.
Also, the first time, the client fetch the notification information in Redis, it will make "READ".
The backend websocket remains live, for future use. For example, B2B integration, which requires low-latency communication.
Sorry, something went wrong.
rtang03
No branches or pull requests
after the authentication to done on ui-control, for each query request. #81 #77 #85
We then implement authenticated subscription upon Event Arrival.
The text was updated successfully, but these errors were encountered: