<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Demystifying HostNameComparisonMode: Wildcards, and URI Matching</title>
	<link>http://kennyw.com/indigo/109</link>
	<description>Kenny Wolf's Thoughts of the Moment</description>
	<pubDate>Tue, 06 Jan 2009 07:19:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: kennyw.com &#187; Blog Archive &#187; What IP Address(es) do we listen on?</title>
		<link>http://kennyw.com/indigo/109#comment-4262</link>
		<author>kennyw.com &#187; Blog Archive &#187; What IP Address(es) do we listen on?</author>
		<pubDate>Sat, 19 Aug 2006 00:20:28 +0000</pubDate>
		<guid>http://kennyw.com/indigo/109#comment-4262</guid>
		<description>[...] For routing traffic, wildcard semantics are in effect, which means that net.tcp://localhost/a/b and net.tcp://127.0.0.1/a/b will match the same set of incoming Messages. The difference is that the first URI is exposed to all interfaces/IP Addresses while the second URI is limited solely to 127.0.0.1. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] For routing traffic, wildcard semantics are in effect, which means that net.tcp://localhost/a/b and net.tcp://127.0.0.1/a/b will match the same set of incoming Messages. The difference is that the first URI is exposed to all interfaces/IP Addresses while the second URI is limited solely to 127.0.0.1. [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
