IIS uses some inscrutable strings to configure the activatable bindings of a web site. Here's the minimum you need to interpret a binding and get started working with activation. Activation is controlled by the activationHost.config file. In the list of web sites, each site has a binding section that contains the list of supported protocols.
<site name="Default Web Site" id="1"> <bindings> <binding protocol="HTTP" bindingInformation="*:80:" /> <binding protocol="net.tcp" bindingInformation="808:*" /> </bindings></site>
The format for the HTTP binding information comes from IIS. It has three parts separated by colons. The three parts are
The format for TCP was picked to be as similar as possible to what already existed for HTTP. We have two parts to configure, again separated by colons. There is no equivalent for the list of addresses. The two parts are
Next time: Proxy Bypassing Behavior
Nicholas, Excuse the dumb question but... are we talking IIS7 here?
The synchronization context is invisible state that flows around making sure that the proper threading
That's right, non-HTTP activation is a new feature of IIS7.
Nicolas,
In some limited experimentation with IIS7, I haven't been able to disable the HTTP binding without causing an error. Can you confirm whether HTTP binding must remain available?
John,
That's an interesting question but unfortunately I don't know. I would be surprised if you couldn't remove HTTP but I don't know what the design is supposed to be. You might be able to get more information from someone that is focused on IIS development.
Yesterday I got the opportunity to start playing with Windows Communication Foundation net.tcp services