Skip to content

Handling reconnection #162

@yallie

Description

@yallie

Is your feature request related to a problem? Please describe.
There are two scenarios of connection loss:

  1. Server was restarted, client session was lost
  2. Network connection was lost, but server session retained

Describe the solution you'd like
Let's talks about the first issue: server was restarted.
Not sure if it's easier to fix, but I believe it's easier to reproduce.

I'd like all clients to be able to silently reconnect and recover their sessions.
This includes session state, authenticated client identity, event handlers, etc.
The framework should be able to notify the clients about the disconnection and reconnection events.

Describe alternatives you've considered
Closing and restarting clients. Actually, not a plausible alternative to reconnection.

Additional context
Zyan.Communication framework supports this for .NET Remoting.
It's able to reconnect, re-login and re-subscribe remote events as if nothing happened.
So I believe it should be possible to implement in CoreRemoting.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions