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.

Sign up for GitHub

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

Jump to bottom

Protocol message to reset client state #1213

Merged
merged 2 commits into from
May 2, 2024
Merged

Protocol message to reset client state #1213

merged 2 commits into from
May 2, 2024

Commits on May 2, 2024

  1. add a reset database command

    @magnetised
    magnetised committed May 2, 2024
    Configuration menu
    Copy the full SHA
    5a7e0cc View commit details
    Browse the repository at this point in the history

  2. Issue client reset message when permissions change (#1218) 

    Rather than attempt to reset the server connection's state after we've
asked the client to reset itself, we just close the connection. The
client will then re-connect automatically and, since it's had its state
reset, the server will treat it as a first connection (including
dropping all client reconnection state).

Since this is intended as an enabling simplification to maintain
consistency between client and server in the simplest way possible,
pending a more efficient, less brutal but much more complicated
solution, I've tried to keep the changes to the protocol as small as
possible.

Hence the use of `throw` -- it's either that or restructure all the
message handling on the server side to be more of a `reduce_while`
style.
    @magnetised
    magnetised committed May 2, 2024
    Configuration menu
    Copy the full SHA
    d464635 View commit details
    Browse the repository at this point in the history