J
Jonny Bergdahl
So far based on my research, at server-side, WCF method can use
Sorry for the late reply, I haven't come around to this until now.
I am sorry to report that this does not seem work. The
OperationContext.Current.InstanceContext.State only seems to track the
internal state of thre service object, and not the communication state.
When I have initiated a connection from the client, State is set top Opened.
But even after I have closed down the Client, it is still set to Opened even
though the HTTP connection is closed.
What I need is to keep track of the underlying HTTP connection state,
something like HttpResponse.IsClientConnected.
Any other ideas on how to get to the underlying connection?
Regards;
/jb
"OperationContext.Current" to inspect some WCF method invocation context
info. And the OperationContext class has a "InstanceContext" property that
can help inspect the current communication object's State:
Sorry for the late reply, I haven't come around to this until now.
I am sorry to report that this does not seem work. The
OperationContext.Current.InstanceContext.State only seems to track the
internal state of thre service object, and not the communication state.
When I have initiated a connection from the client, State is set top Opened.
But even after I have closed down the Client, it is still set to Opened even
though the HTTP connection is closed.
What I need is to keep track of the underlying HTTP connection state,
something like HttpResponse.IsClientConnected.
Any other ideas on how to get to the underlying connection?
Regards;
/jb