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

Fixes socket timeout on non-blocking Connect() #3368

Closed
wants to merge 1 commit into from

Conversation

ThadHouse
Copy link
Contributor

Previously, a non-blocking Connect() call using the IPAddress[] overload would block forever. This does not match either the mono Connect(IPEndPoint) overload or the .NET Core and Windows .NET Framework implementations, which throw the socket exception immediately on a Connect() error. This fixes that error, and allows for a timeout on the Connect() method.

Error reported at https://bugzilla.xamarin.com/show_bug.cgi?id=13416

This change is released under the MIT license.

Previously, a non-blocking Connect() call using the IPAddress[] overload
would block forever. This does not match either the mono
Connect(IPEndPoint) overload or the .NET Core and Windows .NET Framework
implementations, which throw the socket exception immediately on a
Connect() error. This fixes that error, and allows for a timeout on the
Connect() method.

This change is released under the MIT license.
@monojenkins
Copy link
Contributor

Hello! I'm the build bot for the Mono project.

I need approval from a Mono team member to build this pull request. A team member should reply with "approve" to approve a build of this pull request, "whitelist" to whitelist this and all future pull requests from this contributor, or "build" to explicitly request a build, even if one has already been done.

Contributors can ignore this message.

@akoeplinger
Copy link
Member

build

@baulig
Copy link
Contributor

baulig commented Dec 14, 2018

The Socket class has undergone huge refactoring changes. I filed an issue #12072 about this and will close this PR as it does not apply cleanly anymore.

@baulig baulig closed this Dec 14, 2018
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.

6 participants