-
Notifications
You must be signed in to change notification settings - Fork 12
Support more advanced UDP specific features in Sockets library #6
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
Comments
I am interested in this task, so I have already started to work on it :) Before I start to actually implement it, I would share with you the definition of the class.
|
Hi @silent-tech, The current SocketDescriptor / SocketServer / SocketClient classes should already allow handling basic connected UDP sockets, that I think is what you're trying to do looking at your header definition. It probably wasn't clear because of:
I have been adding SocketServer::bind and a simple (connected) UDP socket test (see cf3034e). If you need some more UDP specific features (like unconnected send, multicast addresses or similar additions) I suggest to create a Regarding this issue we can maybe re-target it to add "more advanced UDP features". |
Sockets library only supports TCP so far and adding UDP support would be great 😀
The text was updated successfully, but these errors were encountered: