GitHub user Jens-G opened a pull request:
https://github.com/apache/thrift/pull/452
THRIFT-3000 .NET implementation has trouble with mixed IP modes
Client: C#
Patch: sharpdevel <icode666@github> & Jens Geyer
TcpListener and TcpClient are created based on the capabilities of the used
runtime framework. For windows the changes automatically handle IPv4 and IPv6
sockets. In mono it behaves as before.
When using TcpListener and TcpClient it depends on the network
configuration if IPv4 or IPv6 is used. By upgrading the framework to .NET 4.5
the DualMode can be set on the sockets of the listener and the client. The
sockets then try to establish IPv6 sockets before they fallback to IPv4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Jens-G/thrift THRIFT-3000-csharp-ipv6
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/thrift/pull/452.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #452
----
commit af5f3e6052cb9d14b998d36ea7291a92e598c565
Author: Jens Geyer <[email protected]>
Date: 2015-04-17T18:55:05Z
THRIFT-3000 .NET implementation has trouble with mixed IP modes
Client: C#
Patch: sharpdevel <icode666@github> & Jens Geyer
TcpListener and TcpClient are created based on the capabilities of the used
runtime framework. For windows the changes automatically handle IPv4 and IPv6
sockets. In mono it behaves as before.
When using TcpListener and TcpClient it depends on the network
configuration if IPv4 or IPv6 is used. By upgrading the framework to .NET 4.5
the DualMode can be set on the sockets of the listener and the client. The
sockets then try to establish IPv6 sockets before they fallback to IPv4
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
