|
|
|
|
It WAS(n't just) me: Extend Your WCF Services Beyond HTTP With WAS
|
Had a fun writing this piece with Steve and Dom.
All the talk about service-oriented applications we've been hearing for the past few years has given birth to real frameworks, runtimes, and other bona fide tools for designing, building, and deploying service-oriented connected systems. A good example of this is Windows® Communication Foundation (WCF), which allows you to create services and service consumers in managed code.
One strength of WCF is that you can host WCF-based services in any Windows process, including a console application, a Windows Forms app, or a Windows Presentation Foundation (WPF) UI application. You can even self-host WCF services in long-running Windows NT® services that run in the background working on behalf of a configured identity. WCF services with HTTP-based endpoints can also be hosted inside IIS, much like the traditional Web services as implemented by ASP.NET and ASMX.
If you want to provide robust WCF services through IIS 7.0, it is essential that you understand a new IIS feature called the Windows Process Activation Service (WAS). WAS is a fundamental underlying component of IIS 7.0 that makes it possible to host WCF services beyond HTTP and without having to install the whole IIS package.
The article discusses:
- The architectures and process models of IIS 6.0 and IIS 7.0
- How Web services were hosted in IIS 6.0
- Hosting robust WCF services with IIS 7.0
- How Windows Process Activation Service (WAS) works
- Support for non-HTTP protocols
Read the whole stuff.
|
© 2002 - 2009 by thinktecture, Ingo Rammer and Christian Weyer. All rights reserved.
|
|