title: What does "OperationContext.Current.GetCallbackChannel" actually do?
body: <p>What does OperationContext.Current.GetCallbackChannel actually do? How does it identify each and every client?</p>
  
  <p>I'm facing a problem in my WCF service. If more than two users get connected to the service all the "interesting Changes" i'm sending from service to the clients are going to the second joined user.</p>
  
  <p>For ex, If A, B, C, D joins the service if i send the changes to C and D through callback it is going to B.</p>
  
  <p>Any ideas?</p>
  
  <p><strong>Details</strong>:</p>
  
  <p>Client : ASP.NET web app</p>
  
  <p>Binding: netTCPBinding</p>
  
  <p><strong>Update1</strong></p>
  
  <p>Okie, i've found the cause of the issue. I've hosted the asp.net client in IIS. For example the URL of the client is <a href="http://url1" rel="noreferrer">http://url1</a>. If i open multiple instances of the page in different machine and join the service the callback channel is always pointing to the first instance of the page (i open the site from different machines). But if i host the asp.net client under different sites in IIS the callback channels are unique. Any thoughts on that?</p>