*** MOVED to http://www.sajay.com/post/2009/02/05/Speaking-at-Techready.aspx

This was my first time presenting at Techready . Being a part of the performance dev team in WCF, this would be a natural topic to pick up. The audience was great and we were aware of some of the problems they mentioned and hoping to solve them in the upcoming releases of the framework.  Wenlong gave a pretty deep insight into the guts of the WCF pumps and throttle's and I walked through some of the common scenarios we have discussed with customers and some demos on the tools we use and recommend.

 

Next time - A whole view of the WCF Pump.

Have you ever tried to get CustomBindings equivalent to a StandardBinding or vice versa. Well recently I was asked why a customBinding  like

<customBinding>
  <binding name="Custom">
    <textMessageEncoding />
      <security authenticationMode="UserNameOverTransport">
         <secureConversationBootstrap />
      </security>
    <httpsTransport />
  </binding>
</customBinding>

was not similar to a wsHttpBinding like the following

They do look similar but there are subtle aspects which which probably make them really different. I am not going to call out every difference here and will leave it to you to spot them. The major point here is that this choice can either make or break your app primarily since I work on perf here and choosing the second would be quite a blow to perf if you really don't want the bells and whistles that wsHttpBinding provides, sometimes 4 to 5 times.