Posted By: Charles | Dec 12th, 2006 @ 12:52 PM | 21,792 Views | 6 Comments
Mike Flasko, Program Manager, and Anthony Jones, Software Development Engineer, dig into Winsock and .NET protocol agnostic network development and elaborate on some of the new APIs in the re-written Windows Vista networking stack. Tune in and meet some of the people behind the APIs you rely on when programming network apps on Windows and learn how to build the next generation of network applications by leveraging IPv6.

Resources:

Winsock IPv6 Porting Guide

IPv6 Website

Blog

Think you have found a bug or have a feature ask/suggestion? Report it here.

Media Downloads:
Rating:
0
0
RichardRudek
RichardRudek
So what do you expect for nothin'... :P
Hmm.

In the agnostic C code example, where the Winsock "service" is IPV4 only, but the PC on which it is running has IPv6 as well, surely there is going to be a performance/user experience issue related to timeouts, unless I'm misinterpreting what was said. eg If getaddrinfo() returns multiple IP Addresses, IPv6 and v4, the IPv6 ones are listed first, right ?


EDIT: Removed detracting (grumpy old man) postscript.
RichardRudek
RichardRudek
So what do you expect for nothin'... :P
Charles wrote:

What was the postscript?
C


It wasn't about you, Charles.

Good Interview, BTW.

RichardRudek
RichardRudek
So what do you expect for nothin'... :P
Charles wrote:

[snip]

At any rate, I am more interested in what the postscript contained from a developer feedback point of view, assuming you were venting about networking or C or something that the interviewees (most important, always) could engage....
C


Ah, that's why said it was detracting.

I bitched about about the use of the word "pound" for the "#" symbol (hash or hatch). Then went on to question why it was cool to say "whack" instead of slash... grumpy old man stuff... there, I said it... Smiley
Microsoft Communities