Datasheet

The following lists the various behaviors managed by the Service Runtime layer:

❑ Throttling Behavior: The Throttling behavior determines the number of processed messages.

❑ Error Behavior: The Error behavior specifies what action will be taken if an error occurs during

service runtime.

❑ Metadata Behavior: The Metadata behavior controls whether or not metadata is exposed to the

outside world.

❑ Instance Behavior: The Instance behavior drives how many instances of the service will be

available to process messages.

❑ Message Inspection: Message Inspection gives the service the ability to inspect all or parts of a

message.

❑ Transaction Behavior: The Transaction behavior enables transacted operations. That is, if a pro-

cess fails during the service runtime it has the ability to rollback the transaction.

❑ Dispatch Behavior: When a message is processed by the WCF infrastructure, the Dispatch

Behavior service determines how the message is to be handled and processed.

❑ Concurrency Behavior: The Concurrency behavior determines how each service, or instance of

the service, handles threading. This behavior helps control how many threads can access a given

instance of a service.

❑ Parameter Filtering: When a message is acted upon by the service, certain actions can be taken

based on what is in the message headers. Parameter Filtering filters the message headers and

executes preset actions based on the filter of the message headers.

Messaging

The Messaging layer defines what formats and data exchange patterns can be used during service com-

munication. Client applications can be developed to access this layer and control messaging details and

work directly with messages and channels.

The following lists the channels and components that the Messaging layer is composed of:

❑ WS Security Channel: The WS Security channel implements the WS-Security specification,

which enables message security.

❑ WS Reliable Messaging Channel: Guaranteed message delivery is provided by the WS Reliable

Messaging channel.

❑ Encoders: Encoders let you pick from a number of encodings for the message.

❑ HTTP Channel: The HTTP channel tells the service that message delivery will take place via the

HTTP protocol.

❑ TCP Channel: The TCP channel tells the service that message delivery will take place via the

TCP protocol.

❑ Transaction Flow Channel: The Transaction Flow channel governs transacted message patterns.

❑ NamedPipe Channel: The NamedPipe channel enables inter-process communication.

❑ MSMQ Channel: If your service needs to interoperate with MSMQ, this is the channel that

enables that.

Part I: Introduction to Windows Communication Foundation

05_089842 ch01.qxp 3/5/07 7:02 PM Page 12