-
Notifications
You must be signed in to change notification settings - Fork 176
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
Client to queue request messages to server and resend them when needed #20507
Labels
Comments
3 tasks
caalador
added a commit
that referenced
this issue
Dec 19, 2024
Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout fixes #20507
caalador
added a commit
that referenced
this issue
Dec 19, 2024
Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout fixes #20507
caalador
added a commit
that referenced
this issue
Dec 20, 2024
Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout fixes #20507
caalador
added a commit
that referenced
this issue
Dec 20, 2024
Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout fixes #20507
caalador
added a commit
that referenced
this issue
Dec 20, 2024
Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout fixes #20507
caalador
added a commit
that referenced
this issue
Dec 20, 2024
Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout fixes #20507
caalador
added a commit
that referenced
this issue
Dec 20, 2024
Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout fixes #20507
caalador
added a commit
that referenced
this issue
Dec 23, 2024
Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout fixes #20507
caalador
added a commit
that referenced
this issue
Jan 2, 2025
Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout fixes #20507
caalador
added a commit
that referenced
this issue
Jan 3, 2025
Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout fixes #20507
caalador
added a commit
that referenced
this issue
Jan 8, 2025
Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout fixes #20507
caalador
added a commit
that referenced
this issue
Jan 9, 2025
Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout fixes #20507
7 tasks
caalador
added a commit
that referenced
this issue
Jan 13, 2025
Add sent payloads to message queue and resend if no response to message inside MaxMessageSuspendTimeout fixes #20507
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Client should queue all send requests and only send the next after previous has received a response.
Server always responds to the client message.
We already have the ServerRpcQueue that queues invocations to be sent and are sent in order when MessageHandler has handled json and runs
processMessage
or inhandleJSON
when old package is receivedLooking at components at least SpreadSheet uses send directly:
The text was updated successfully, but these errors were encountered: