- ASP.Net Compatibility: It should be enabled when hosing service under ASP.Net and need to use asp.net features like HttpContext
- Instancing Mode
- PerCall: A new InstanceContext (and therefore service object) is created for each client request.
- PerSession: A new InstanceContext (and therefore service object) is created for each new client session and maintained for the lifetime of that session (this requires a binding that supports sessions).
- Single: A single InstanceContext (and therefore service object) handles all client requests for the lifetime of the application.
- Concurrency
- Concurrency is the control of the number of threads active in an InstanceContext at any one time. The following three concurrency modes are available:
- Single: Each instance context is allowed to have a maximum of one thread processing messages in the instance context at a time. Other threads wishing to use the same instance context must block until the original thread exits the instance context.
- Multiple: Each service instance can have multiple threads processing messages concurrently. The service implementation must be thread-safe to use this concurrency mode.
- Reentrant: Each service instance processes one message at a time, but accepts re-entrant operation calls. The service only accepts these calls when it is calling out through a WCF client object.
- Durable Services
- Service Throttling
- Serialization
- Data Contract Serialization
- XML Serialization
- Reliable Sessions: This actually implements WS-Reliable Messaging protocols and ensures that messages will be delivered exactly once in in the order it was sent, even if connection itself is not reliable. http://msdn.microsoft.com/en-us/library/ms733136(v=vs.110).aspx
- Call Back Contract: An ASync mechanism in which service notifies the client once operation is complete.
|
|