Parsing Standard Uris, Part 2

Here’s another look at defining what it means to have a URI for the TCP or named pipe transports. You can compare these definitions to the version I gave yesterday using the parser syntax flags. I’ll only cover the net.tcp URI scheme as the two are almost identical except for the use of ports. What…

2

Parsing Standard Uris

The System.Uri class has built-in parsing rules for a variety of schemes, including http, https, file, ftp, gopher, mailto, news, nntp, telnet, and ldap. There are also parsers for the WCF net.tcp and net.pipe schemes. These parsing rules allow a uri using the scheme to be recognized, broken into its component parts, and validated for…

0

Frequently Asked Uri Questions

The System.Net team has put together a list of frequently asked questions for the System.Uri class that they’re responsible for. The Uri is one of the few types that we use quite extensively in the programming model for WCF but don’t implement ourselves. There are a small number of features that have been added to…

1

Some History of the Named Pipe, Part 4

Here are the past articles in the series to get up to date: Some History of the Named Pipe, Part 1 (Unix pipes) Some History of the Named Pipe, Part 2 (Unix fifo) Some History of the Named Pipe, Part 3 (Windows named pipe) The last part in this series is to bring the history…

2

Some History of the Named Pipe, Part 3

Some History of the Named Pipe, Part 1 (Unix pipes) Some History of the Named Pipe, Part 2 (Unix fifo) Some History of the Named Pipe, Part 3 (Windows named pipe) Some History of the Named Pipe, Part 4 (WCF named pipe) In earlier parts we looked at the anonymous pipe and the fifo, which…

0

Some History of the Named Pipe, Part 2

Some History of the Named Pipe, Part 1 (Unix pipes) Some History of the Named Pipe, Part 2 (Unix fifo) Some History of the Named Pipe, Part 3 (Windows named pipe) Some History of the Named Pipe, Part 4 (WCF named pipe) The anonymous pipes that I talked about last time satisfy the basic requirements…

0

Some History of the Named Pipe, Part 1

Some History of the Named Pipe, Part 1 (Unix pipes) Some History of the Named Pipe, Part 2 (Unix fifo) Some History of the Named Pipe, Part 3 (Windows named pipe) Some History of the Named Pipe, Part 4 (WCF named pipe) Let’s start with the more ancient history and work over a few steps…

2

Windows API Code Pack V1 Released

Going along with Windows 7, the final version of the Windows API Code Pack was released last week. The code pack is a way to provide access to Windows features that lack a managed interface in the framework today, primarily for things added in Windows Vista and Windows 7. For example, the code pack adds…

0

What Will Be New in Networking for Beta 2

The NCL team has released their list of new networking features for .Net framework 4 beta 2. A partial summary of the features is: Opening socket connections using the DNS name of the machine Opening socket connections for IPv4 and IPv6 simultaneously Using SSL for authentication only Setting 64-bit values for the HTTP Range header…

0

Finding Free Ports, Part 2

Yesterday I talked about the algorithm the TCP transport uses to reserve a unique port when listening on both IPv4 and IPv6 addreses is enabled for a service. Why are the random port numbers drawn from the range 49152-65535? Because that’s the range the operating system uses for dynamic port allocations. Sometimes. The IANA divides…

0