-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Updated UdpConnection to match TcpConnection send semantics #3053
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
Updated UdpConnection to match TcpConnection send semantics #3053
Conversation
@Horusiath oh snap, I was in the middle of implementing this myself. I'll review yours instead |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've pulled this down to my local machine and added some tests, which do not pass. Going to push some changes back shortly.
@@ -34,7 +34,7 @@ protected override bool Receive(object message) | |||
{ | |||
case UdpConnected.Connect connect: | |||
{ | |||
var commander = Sender; | |||
var commander = Sender; // NOTE: Aaronontheweb (9/1/2017) this should probably be the Handler... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like a bug to me; the .Handler
property on the Connect
message is never actually used... But changing it now would be a breaking change for anyone who has ever used this feature. Decided to just take note of it and punt on it until a later time in the interests of fixing sending behavior first.
This PR aims to provide the same send semantics over UDP connection, as the one used by TcpConnection, that were introduced by @Aaronontheweb in #3023