Building Windows runtime sockets apps

Play Building Windows runtime sockets apps
Sign in to queue


Today's networks have grown more complicated as a result of multihoming, web proxies, security issues, internationalization and other issues. Because dealing with these complexities is hard, it is either ignored or significant resources are spent attempting to do so. In this session, we will demonstrate how the Windows Runtime sockets API simplifies what an app must do to use TCP or UDP. We also will present exciting new functionality, such as proximity discovery and using WebSockets for HTTP proxy traversal, as well as how to handle complex security and cost issues.









Download this episode

The Discussion

  • User profile image

    Can we get a better format video? There's only one and reading the code/text is difficult and impossible in some parts.


  • User profile image

    See also the content video about Multicast for LAN discovery --


  • User profile image

    For each ipv4 or ipv6 address, there are 65535 port numbers. Some are well-known and some are not. The range 49152-65535 are private port numbers (ie, not well-known like 80 for HTTP, or 25 for SMTP) and can be used at will by the user without fear of colliding with IANA port-numbers that have been set aside for powerful corporations like Microsoft, Cisco and IBM. The IP address plus the port number constitutes the endpoint. You were referring to the port number as being universal for all IP addresses which is not correct for the private range. With the advent of IPv6, this habit IANA has of granting universal port numbers will discontinue. Therefore, it is not proper to refer to a port number is as being a "service name", but merely as one of 65535 numbers associated with a particular IP address, IPv4 or IPv6. Endpoint is the proper term. Your ConnectAsync method establishes an endpoint.

Add Your 2 Cents