StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14795909
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-10T08:11:40.957
FavoriteCount
0
LastActivityDate
2013-02-10T08:11:40.957
LastEditDate
LastEditorUserId
0
OwnerUserId
448407
ParentId
4036488
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
I am not sure but here is how I understand this for a Duplex mode communication. I had a look at the InstanceContext class defined in the System.ServiceModel assembly using dotPeek decompiler. Internally there is a call <pre><code>this.channels = new ServiceChannelManager(this); </code></pre> That means, it is creating channel using a ServiceChannelManager passing in the instance of the same InstanceContext. This way it keeping a track of the Channel with the instance of InstanceContext. Then is binds Incoming channel (Service to Client) requests in method that is implemented as : <pre><code>internal void BindIncomingChannel(ServiceChannel channel) { this.ThrowIfDisposed(); channel.InstanceContext = this; IChannel channel1 = (IChannel) channel.Proxy; this.channels.AddIncomingChannel(channel1); if (channel1 == null) return; switch (channel.State) { case CommunicationState.Closing: case CommunicationState.Closed: case CommunicationState.Faulted: this.channels.RemoveChannel(channel1); break; } } </code></pre> So to answer your queries : a. Yes, it internally maintains the Service and InstanceContext (which creates a channel) relations for calls between Client and Service. b. Yes, the channel needs to stay opened untill the Service replies back to the context, in which the InstanceContext will take care of closing the channel. c. Each client has a unique Session Id, but the InstanceContext type at the Service depends on the InstanceContextMode used at the Service on the implementation of the Contract. d. It uses the same channel. InstanceContext maintains a count of IncomingChannel and Outgoing channel. Incoming channel are the one that are Service to Client directed and Outgoing are Client to Service directed. You can see this count using debugger in VS. For the sake of further clarification, as far as the other behavior for a Duplex service is concerned, here is how we can look at the behavior of InstanceContext and how channel instance is created : I created a Duplex service demo : <pre><code>[ServiceContract(SessionMode = SessionMode.Required, CallbackContract = typeof(IServiceDuplexCallback))] public interface IServiceClass { [OperationContract(IsOneWay = true)] void Add(int num1); } </code></pre> This contract is implemented as : <pre><code>[ServiceBehavior(InstanceContextMode = InstanceContextMode.PerCall)] public class ServiceClass : IServiceClass { int result = 0; public void Add(int num1) { result += num1; callBack.Calculate(result); } IServiceDuplexCallback callBack { get { return OperationContext.Current.GetCallbackChannel<IServiceDuplexCallback>(); } } } </code></pre> In this implementation notice the first line where InstanceContextMode is set to PerCall. The default is PerSession. This enumeration has three options: <ol> <li>PerCall - New instance of InstanceContext used for every call independent of Session</li> <li>PerSession - New instance used for every session</li> <li>Single - A single instance of InstanceContext used for all the clients.</li> </ol> I created a client which use NetTcpBinding to connect with Service : <pre><code>InstanceContext ic = new InstanceContext(new TCPCallbackHandler(ref textBox1)); TCP.ServiceClassClient client = new TCP.ServiceClassClient(ic); // First call to Add method of the Contract client.Add(val1); // Second call to Add method of the Contract client.Add(val2); </code></pre> TCPCallbackHandler is the class in the Client that implements the Callback contract as: <pre><code>public class TCPCallbackHandler : TCP.IServiceClassCallback { TextBox t; public TCPCallbackHandler(ref TextBox t1) { t = t1; } public void Calculate(int result) { t.Text += OperationContext.Current.SessionId + " " + result.ToString(); } } </code></pre> To see the behavior of the InstanceContext, I started the service and then started two clients with each enumeration operation as discussed above. Here are the results : 1 - PerCall Client 1 : urn:uuid:4c5f3d8b-9203-4f25-b09a-839089ecbe54 5 - urn:uuid:4c5f3d8b-9203-4f25-b09a-839089ecbe54 5 Client 2 : urn:uuid:e101d2a7-ae41-4929-9789-6d43abf97f01 5 - urn:uuid:e101d2a7-ae41-4929-9789-6d43abf97f01 5 Here - urn:uuid:4c5f3d8b-9203-4f25-b09a-839089ecbe54 is SessionId Since for each client Add is called twice in the Client, and in PerCall -> new instance of InstanceContext is created every call, we create a new instance of ServiceClass for both the calls of every client. Point to note here is that new instance is created even for the same session // First call to Add method of the Contract client.Add(val1); -> New Instance of ServiceClass created and value will be incremented to 5 // Second call to Add method of the Contract client.Add(val2); -> New Instance of ServiceClass created and value will be incremented to 5 2 - PerSession Client 1 : urn:uuid:4c5f3d8b-9203-4f25-b09a-839089ecbe54 5 - urn:uuid:4c5f3d8b-9203-4f25-b09a-839089ecbe54 10 Client 2 : urn:uuid:e101d2a7-ae41-4929-9789-6d43abf97f01 5 - urn:uuid:e101d2a7-ae41-4929-9789-6d43abf97f01 10 Here the instance of ServiceClass is separate for both the client as they have different sessions running. So the increment in the calls is 0 -> 5 -> 10 (for both client separately) 3 - Single Client 1 : urn:uuid:4c5f3d8b-9203-4f25-b09a-839089ecbe54 5 - urn:uuid:4c5f3d8b-9203-4f25-b09a-839089ecbe54 10 Client 2 : urn:uuid:e101d2a7-ae41-4929-9789-6d43abf97f01 15 - urn:uuid:e101d2a7-ae41-4929-9789-6d43abf97f01 20 Here the same instance of ServiceClass is shared by all clients so we have 0 -> 5 -> 10 in first client. The second client will increment in the same instance, so we get 10 -> 15 -> 20. This will behave differently as per the call and may give result like when invoked at the same time from the clients. Client 1 : urn:uuid:4c5f3d8b-9203-4f25-b09a-839089ecbe54 5 - urn:uuid:4c5f3d8b-9203-4f25-b09a-839089ecbe54 15 Client 2 : urn:uuid:e101d2a7-ae41-4929-9789-6d43abf97f01 10 - urn:uuid:e101d2a7-ae41-4929-9789-6d43abf97f01 20 Hope this helps!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow does in duplex system WCF differentiate between different channel instances?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDinesh
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTBountyClose
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.