In WCF, the powerful OperationContext.Current static property lives in thread-local storage. It gets pinned to the current thread before WCF dispatches to the user code. If code for a service operation - for whatever reasons - is spawning new threads to do its work the current OperationContext object will have to be captured and needs to be passed to the other threads.
Just to let you know.
Just to let you know.
Why not provide some sample code on how to do that? Whats the TLS slot to put the OperationContext into, so also other threads can access it via OperationContext.Current?
Posted by: Ralf | 05/05/2007 at 08:54 PM