PNASoft
RSS feed

Summarize

Galleries: 68   Photos: 2224
Folders: 67   Files: 2221
Members: 34756      


OReilly - Programming WCF Service

OReilly - Programming WCF Service

Preface

In August 2001 I first learned the details of an effort in Microsoft to rewrite COM+ using managed code. Nothing much happened after that. Then, in July 2002, during a C# 2.0 Strategic Design Review, the remoting program manager outlined in broad strokes plans to rework remoting into something that developers should actually use. At the same time, Microsoft was also working on incorporating the new security specs for web services into the ASMX stack and actively working with others on drafting a score of additional web services specs.

In July 2003 I was given access to a new transactional infrastructure that improved on the deficiencies in transactional .NET programming. As of yet, there was no cohesive programming model that unified these distinct technologies. Towards the end of 2003 I was privileged to be invited to join a small team of outside industry experts and participate in the strategic design review of a new development platform code- named Indigo. Some of the smartest and nicest people I know were part of that team. Over the next 23 years Indigo went through some three generations of programming models. The current declarative, endpoint-driven object model debuted in early 2005, was stabilized by August of that year, and was named the Windows Communication Foundation (WCF).

It is difficult to get a consistent answer from different people on what WCF is. To the web service developer, it is the ultimate interoperability solution, an implementation of a long list of industry standards. To the distributed application developer, it is the easiest way of making remote calls and even queued calls. To the system developer, it is the next generation of productivity-oriented features, such as transactions and hosting, that provide off-the-shelf plumbing for applications. To the application developer, it is a declarative programming model for structuring the application. And to the architect, it is how one can finally build service-oriented applications. WCF is in actuality all of those, simply because it was designed that wayto be the unified next generation of Microsoft's disparate technologies.


Google bookmark Yahoo bookmark Digg bookmark Furl bookmark Reddit bookmark Slashdot bookmark Stumbleupon bookmark Technorati bookmark Blinklist bookmark Newsvine bookmark Netvouz bookmark Wists bookmark Blogmarks bookmark Spurl bookmark Shadows bookmark Facebook bookmark
Placeholder for Google Adsense
Placeholder for Google Adsense



Comments

Lilanga said:

Actually nice book and going step by step to deep concepts. Thanks for sharing

December 22, 2008 1:54 PM
PNASoft.com does not store any files on its server.
Please contact the content providers to delete copyright contents. Copyright by PNASoft.com