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

Implement server side disconnect packet #45

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

PabloMK7
Copy link
Contributor

Implements the method Disconnect in PRUDPEndPoint, which allows disconnecting a PRUDPConnection by sending it a DISCONNECT packet. The connection will be cleaned up after it times out or a disconnect acknowledgement packet is recieved back.

prudp_endpoint.go Outdated Show resolved Hide resolved
prudp_endpoint.go Outdated Show resolved Hide resolved
@PabloMK7 PabloMK7 requested a review from DaniElectra April 17, 2024 16:09
connection.cleanup()
pep.Connections.Delete(discriminator)

pep.emit("disconnect", disconnect)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need this? We already have the "connection ended" event anyway

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The emit? What's it's purpose anyways?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The purpose of emit is to send event signals to listeners. We don't personally make use of all of them, but another developer may find them useful in their own servers (such as more detailed logging at the packet level). The syn, connect, disconnect and data events are emitted when packets of those types are received. Though looking at the code again, we only expose the disconnect and data packet events (in previous versions of the library the On method was exported and could be used to listen for any packet type, but this was removed in favor of specific OnData and OnDisconnect methods)

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

Successfully merging this pull request may close these issues.

3 participants