Welcome to Windows Communication Foundation (WCF)
Top Tasks :

WCF Team Bloggers

Friday, June 30, 2006 - Posts

  • Microsoft Pro Photo Summit

    This week was Microsoft's first Pro Photo Summit. It featured the launch of a program called Icons of Imaging, designed to showcase the work of leaders and innovators in photography; and the announcement of the winners of a Future Pro Photographer Contest. The inaugural summit introduced the first six "imaging icons", an array of photographers whose specialties range from nature to celebrities to weddings, and who are recognized around the world as leaders in their specialty area of photography. Bambi Cantrell Reed Hoffmann Denis Reggie John Shaw Matthew Jordan Smith Art Wolfe A panel of judges also selected an overall winner and three runners-up in the Future Pro contest, which Microsoft says had 13,000 entries from 92 countries. The grand prize went to a Romanian entrant. Related stories: C-net News: "Microsoft woos digital-photography enthusiasts"... Read More...
  • Some Changes for Channels and Transports in the June CTP, Part 4

    Yesterday's post covered most of the big new features that were added in the latest release . Today I'll go through the rest of the new features that are smaller in scope although no less exciting. #1: When the channel stack is being built from binding elements, some binding elements want to know what elements are underneath of them so that they can properly configure themselves. Previously, there was no way for custom binding elements to get at this information. We made the RemainingBindingElements property on the binding context public so that your binding elements can work exactly the same as ours. #2: Transport stream upgrades frequently operate on a point-to-point basis, but the API for providing stream upgrades previously only gave the upgrade provider the final address of the connection. We've changed the interface for StreamUpgradeProvider so that upgrades can see both the endpoint address and the via address of the next hop. #3: It's now possible to disable the use of HTTP keep alive. We added a KeepAliveEnabled option to HttpTransportBindingElement with the default set to enabled, which was the old behavior. This option is only available on the binding element so you'll need to use a custom binding if you need to change this setting. #4: There's now a quota setting for how long a connection can take to authenticate. A client needs to send a few hundred bytes of data before the server has enough information to perform authentication. Previously, the client had the entire receive timeout in which to send this data. The header is often much smaller than a normal sized message and clients are anonymous until this information is processed. The ChannelInitializationTimeout on the binding element limits the amount of time a malicious client can tie up one of the connections for your server. We also changed a few interfaces into abstract base classes although we didn’t add any new functionality to those classes at this time. The IRequestContext interface is now the RequestContext class and the IStreamUpgradeBindingElement interface is now the StreamUpgradeBindingElement class. I had a list of changes that I was hoping to get through during this week. However, the first two days ran a little bit long so there are still a few more items to cover. I'll run one more installment of this series on Monday and the next set of topics will start after the 4th of July holiday. Next time: Some Changes for Channels and Transports in the June CTP, Part 5 Read More...
  • Here, belatedly, are the slides on building manageable applications with the Windows Communication Foundation

    The slides from my Tech-Ed Boston 2006 talk and my presentation to the Seattle .NET users' group are here: http://www.electronicfiles.net/files/3741/CON328.zip . Sorry for my delay in posting them. Read More...
  • Windows Communication Foundation Hands-On June 2006 CTP/RC1 Updates: Chapter Eight

    New code to accompany chapter eight of Microsoft Windows Communication Foundation-Hands On! , compatible with the June 2006 CTP/RC1 release is here: http://www.electronicfiles.net/files/3741/08.zip . I prefer this sample to the original one because it covers a more common scenario. The scenario is that of a server application that communicates via a proprietary protocol over TCP. That protocol defines how messages are framed within data transmitted via the TCP socket, and how messages may be formatted. Client applications connect to the server and the client and server send messages back and forth to one another, in response to events occuring one the client's side, or on the server's. Run the sample without debugging to avoid a couple of phantom exceptions. The June 2006 CTP/RC1 release itself is here: http://www.microsoft.com/downloads/details.aspx?FamilyID=8d09697e-4868-4d8d-a4cf-9b82a2ae542d&DisplayLang=en . Read More...

Copyright © 2006 Microsoft Corporation. All Rights Reserved. | Terms of Use | Privacy Statement | Contact Us