StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2247309
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-02-11T19:57:42.093
FavoriteCount
0
LastActivityDate
2015-10-22T01:35:27.567
LastEditDate
2015-10-22T01:35:27.567
LastEditorUserId
1094609
OwnerUserId
41898
ParentId
1618240
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
The socket API is governed by IETF RFCs and should be the same on all platforms including windows WRT IPv6. For IPv4/IPv6 applications it's ALL about <code>getaddrinfo()</code> and <code>getnameinfo()</code>. <code>getaddrinfo</code> is a genius - looks at DNS, port names and capabilities of the client to resolve the eternal question of “can I use IPv4, IPv6 or both to reach a particular destination?” Or if you're going the dual-stack route and want it to return IPv4-mapped IPv6 addresses, it will do that too. It provides a direct <code>sockaddr *</code> structure that can be plugged into <code>bind()</code>, <code>recvfrom()</code>, <code>sendto()</code> and the address family for <code>socket()</code>… In many cases this means no messy <code>sockaddr_in(6)</code> structures to fill out and deal with. For UDP implementations I would be careful about setting dual-stack sockets or, more generally, binding to all interfaces (<code>INADDR_ANY</code>). The classic issue is that, when addresses are not locked down (see <code>bind()</code>) to specific interfaces and the system has multiple interfaces requests, responses may transit from different addresses for computers with multiple addresses based on the whims of the OS routing table, confusing application protocols—especially any systems with authentication requirements. For UDP implementations where this is not a problem, or TCP, dual stack sockets can save a lot of time when IPv*-enabling your system. One must be careful to not rely entirely on dual-stack where it`s not absolutely necessary as there are no shortage of reasonable platforms (Old Linux, BSD, Windows 2003) deployed with IPv6 stacks not capable of dual stack sockets.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to support both IPv4 and IPv6 connections
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCraig M. Brandenburg
UserOwnerUserId
1. USEinstein
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.