http://kennyw.com/work/indigo/109 Kenny Wolf Tue, 15 May 2012 15:20:56 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://kennyw.com/work/indigo/109/comment-page-1#comment-218114 Locating a WCF named pipe endpoint - Chris Dickson's Blog Wed, 20 Oct 2010 17:27:01 +0000 http://kennyw.com/indigo/109#comment-218114 [...] support, determines the URL matching rules which will be applied for a particular service endpoint. A post by Kenny Wolf some time ago explains this mechanism in detail. The WCF client doesn’t know whether its configured service URL [...] [...] support, determines the URL matching rules which will be applied for a particular service endpoint. A post by Kenny Wolf some time ago explains this mechanism in detail. The WCF client doesn’t know whether its configured service URL [...]

]]> http://kennyw.com/work/indigo/109/comment-page-1#comment-4262 kennyw.com » Blog Archive » What IP Address(es) do we listen on? Sat, 19 Aug 2006 00:20:28 +0000 http://kennyw.com/indigo/109#comment-4262 [...] 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. [...] [...] 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. [...]

]]>