views:

302

answers:

1

I'm currently working on a WCF service that reaches out to another service to submit information in a few of its operations. The proxy for the second service is generated through the strongly typed ProxyFactory<T> class. I haven't experienced any issues but have heard I should do something like the following when making the call:

using (new OperationContextScope((IContextChannel)_service))
     _service.Send(message);

So my question is: when is creating this new OperationContextScope appropriate, and why?

Thanks!

+1  A: 

If you are using callbacks or if you want to modify the message or headers then u need to use OperationContextScope .Your service might be need to modify outgoing headers while calling that another service.

When you establish OperationContextScope then you can 1) Access and modify incoming and outgoing message headers and other properties.

2) Access the runtime, including dispatchers, the host, channel, and extensions.

3) Access other types of contexts, such as security, instance, and request contexts.

4) Access the channel associated with the OperationContext object or (if the channel implements System.ServiceModel.Channels..::.ISession) the associated channel's session identifier.

The another service which you call , is it session based service ? Probly you need to look at its sample client code or documentation if available.

Ajax2020
Gotcha. So anytime I want more granular control over session information, security, etc. I should establish a separate `OperationContextScope`. The other service is session-based, yes.
Brandon Linton