Behaviors(Essential Windows Communication Foundation)

　　WCF implements short-lived, ACID-style transactions in behaviors. Transactions can exist within a service or can flow across service boundaries. Transactions are implemented at the operation behavior level, although certain conditions must be met at the endpoint and service level. For instance, to flow transactional context from the client to the service, the service endpoints must use a protocol that supports sessions, such as wsHttpBinding. Sessions must be allowed at the service level to flow transactions across service boundaries. Operation behaviors enable developers to specify the isolation level of transactions, and administrators can control the timeout properties.

　　WCF supports three transaction managers, one for local transactions within a process, one for Vista-only resources, and the Distributed Transaction Coordinator. In addition, communication across service boundaries can use either a Windows-only transaction protocol that leverages RPC, or it can use the standards-based WS-AT protocol.