Chapter 1. User Interface Changes
What is the single biggest way that IPv6 may bite you as an application developer? Sure, if you are dealing with network applications like, say, Wireshark, you’re going to be hit by changes down at the socket level. But for the vast majority of applications, which simply need to interact with other applications at a network layer, what is the biggest change?
The user interface!
“Huh?” you might be asking yourself…but think about it. How many times have you looked at an application’s “Preferences” or “Options” window and seen a screen like this:

How well will that work with an IPv6 address?
In fact, as I was first writing this book, I happened to notice that the game Minecraft had a new release. One of the many changes was related to the format of the IPv6 address being entered into the app:
* Fixed IPv6 addresses being parsed wrongly. To connect to a specific port in IPv6, use the format [1234:567::1]:25565
These are just two of the many little ways that IPv6 will mess with your mind and with your app. You’ll need to think about and investigate how you present IP addresses for display and how you accept IP addresses for input. This may, surprisingly, be the area that will cause you the most pain and require the most testing. Ideally, we will move away from using IP addresses and toward using DNS domain names, but in some cases, you may still need to accept ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access