You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I want to make an example that e.g. sends a message right after every received message, would it be best to have separate classes InUDPClient and OutUDPClient, or would it be just as fine having a class UDPClient that does both receiving and sending?
I guess receiving and sending should be on separate ports, e.g. 6447 and 6448.
The text was updated successfully, but these errors were encountered:
From a technical standpoint, using the same socket for sending and receiving is allowed. So from there it's a design question, based on the needs of your application.
If I want to make an example that e.g. sends a message right after every received message, would it be best to have separate classes InUDPClient and OutUDPClient, or would it be just as fine having a class UDPClient that does both receiving and sending?
I guess receiving and sending should be on separate ports, e.g. 6447 and 6448.
The text was updated successfully, but these errors were encountered: