You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Client restart handling is bad. Connector app may start processing the commands from the restarted app in the same environment as it was before the restart, but then, after some time, it will realize that the client app has been restarted - and it will clean up and destroy all handles and start with a clean environment after this point - which really puts the client into a weird state. The commit 215d5ba has a temporary workaround for this, allowing the client to wait until the full "handshake" finishes before sending the commands.
The timeouts for sending ping messages and for considering the Connector app as dead have to be hardcoded based on the sources of the Connector app.
There's no way in the protocol to send a generic error from the Connector app to the client (like "permission denied" or "received message has invalid format").
Asymmetry between "ping" requests and "pong" responses is a complication that brings not many benefits.
The text was updated successfully, but these errors were encountered:
The existing protocol has several issues, mainly:
The text was updated successfully, but these errors were encountered: