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.

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 callback OnDisconnected always being called twice #126

Open
PyrateAkananto opened this issue Nov 29, 2022 · 3 comments
Open

client callback OnDisconnected always being called twice #126

PyrateAkananto opened this issue Nov 29, 2022 · 3 comments

Comments

@PyrateAkananto
Copy link
Contributor

The intention of pull #121 from @imerr was to have the callback client.OnDisconnected being called within the client even in case of socket errors or different exceptions.

I think that intention was fulfilled. This can be verified for example by calling client.Connect("localhost", 13378888); which uses an invalid port.

On the other hand I think that the change had unintended side effects. In my project I can see that within the client during regular, error-free use the callback client.OnDisconnected is always called twice. It does not matter whether the client or the server initiated the disconnect.

In my opinion that callback should only be called once (not twice).

My knowledge about Telepathy is not good enough to suggest an improvement or even create a pull request, sorry.

@marek-stoj
Copy link

I've encountered the same issue. I think that the #121 change is incorrect. I'm getting the Disconnected event without it. Just make sure to always call client.Tick() in the Unity's Update loop even if the client is not connecting/connected. Maybe that was the root cause of @imerr's issue that prompted him to implement that "fix" (?)

@noxowl
Copy link

noxowl commented Oct 3, 2023

Do we have a solution yet?

@PyrateAkananto
Copy link
Contributor Author

#121 is listed in the change log of V1.9 (cbdf3dc).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants