Improve connection handshake when EndPoint is already in use - Githubissues

Kittyfisto / SharpRemote

A .NET remoting library

MIT License

12 stars 5 forks source link

Improve connection handshake when EndPoint is already in use #49

Closed Kittyfisto closed 6 years ago

Kittyfisto commented 6 years ago

Currently when a server Endpoint is in use and another EndPoint establishes a connection, then the error being received is not really helpful: SharpRemote.Exceptions.HandshakeException: Some Endpoint Name: EndPoint '' did not receive 'auth challenge' message from remote endpoint 'X.Y.Z.W:40001' in time: 9,9979998s (error: TimedOut)

This should be improved so that

The client-endpoint receives a message which tells it why the connection was immediately closed again
The client-endpoint does not have to wait until its timeout is reached (which is 10 seconds by default)

Kittyfisto commented 6 years ago

From now on, a RemoteEndpointAlreadyConnectedException is thrown whenever a connection to another already connected endpoint is established. Will be available with the next patch.