问题描述
我开发使用许多语言和一些平台的应用。从我读什么，IPv6的将是那么未来5 - 10年内的主流，而一些ISP甚至提供到IPv6 Internet的直接连接。在我的私有网络，所有的机器都双栈连接和使用IPv6相互通信时可能的。
I develop applications using many languages and a few platforms. From what I am reading, IPv6 is going to be mainstream within then next 5–10 years, and that some ISPs even offer direct connection to the IPv6 Internet. On my private network, all the machines have dual stack connectivity and communicate with each other using IPv6 when possible.
我的问题是：应该我新的应用程序被写入到支持IPv6？如果是这样，什么是我需要考虑的事情？是否有任何缺点支持IPv6呢？
My question is: should my new application be written to support IPv6? If so, what are the things I need to consider? Are there any downsides to supporting IPv6 now?
我不知道这是否会帮助或伤害，但这里有一些更具体的细节，也许直接的答案一点：
I don't know if this will help or hurt, but here are some more specific details to maybe direct the answers a little:
我的应用程序将在Windows / Linux的/ Mac上运行，这将包括为每个平台分别写了一个特定于平台的组成部分，并写在一个跨preTED语言一个共同的核心组成的。
My app would run on Windows/Linux/Mac, and it would consist of a platform–specific component written separately for each platform, and a common "core" component written in an interpreted language.
我的应用程序应该能够找到在任何三个平台上运行的自身其他实例，并支持任意两台机器之间的TCP和UDP。
My app should be able to locate other instances of itself running on any of the three platforms, and support both TCP and UDP between any two machines.
推荐答案
是所有的新的应用程序应该支持IPv6。正如你说你自己，它已经被许多局域网环境中使用。
Yes: all of your new applications should support IPv6. As you've said yourself, it is already being used in many LAN environments.
否：你不应该为了支持IPv6太大变化。基本架构应该为你的差异照顾。这是假设你没有做像储存或以其他方式操纵的IP地址坏的东西。
No: you shouldn't have to change much in order to support IPv6. The underlying framework should take care of the differences for you. This assumes that you aren't doing "bad" things like storing or otherwise manipulating IP addresses.
这篇关于由于IPv6的是要取代IPv4，我要发展我的新的应用程序来支持它？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！