duplex

I'm writing a service that allows users to register with it and receive notifications when an event happens. I'm trying to do this with netTcpBinding, but keep coming up with errors, even when running on my local machine. When I try to send a notification, I am timing out, getting this error: Stream Security is required at http://www.w3.org/2005/08/addressing/anonymous , but no security context was negotiated. This is likely caused by the remote endpoint missing a StreamSecurityBindingElement from its binding. For testing I am hosting the service in a console, and it is opening for me and I

What does OperationContext.Current.GetCallbackChannel actually do? How does it identify each and every client? 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. 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. Any ideas? Details : Client : ASP.NET web app Binding: netTCPBinding Update1 Okie, i've found the cause of the issue. I've hosted the asp.net client in IIS. For example the URL of

After developing mini project with WCF duplex (Chat Service | Sms Service), I got a Point that maybe not be correct!! I believed Duplex theory is good and useful but there is a lot problem about using Wcf Duplex . (like reliable session, Time-out exceptions, Client address-Management on server side, proxy management on Client Side) am I think wrong ? am I miss something? For more Information I Used wsDualHttpBinding not tcpBinding. If you need bidirectional communication and you want to use WCF, duplex channels are the way to go. You just need to design your application correctly and correctly

I can't deny the performance benefit of a duplex async call, but some things about makes me feel wary. My concern is that given a client object instantiated, will WCF be able to tell which particular client service instance will receive the callback argument? Can anyone tell me if this is a good idea? If not why not? new DuplexChannelFactory<IServerWithCallback>( new ClientService(), new NetTcpBinding(), new EndpointAddress("net.tcp://localhost:1234/"+Guid.NewGuid())) If the virtual path above is reserved how can it be discarded. I want the client service lifetime to be fairly short. IE make a

I have to design and implement a way to deal with long running processes in a client/server application. A typical long running process would/could take 2-3 minutes. I also need to report progress to the UI in the meantime and keep the UI responsive. Having these in my mind I though of a few solutions: One async request to start the process which starts the server-side process and returns an assigned LRPID (Long Running Process ID) then poll periodically from the client using that LRPID. ( Pro : simple to deploy, no firewall messing around Con : Unelegant, resource consuming etc.) Use a duplex

Renewing the bounty AGAIN because I really need to know how to get this to work, or a definitive answer about why it won't. I've added an alternative explanation of the problem here. Having a hell of a time getting a two-way (IsOneWay = false) WCF client-server to work in .Net 3/3.5. After the client successfully enrolls with the service, the service's periodic Announcement() calls-back to the enrolled clients. It is now that either the client or the server hangs until the server's SendTimeout, adjusted to 2 seconds, elapses. Then the server side has a timeout exception as follows. Only then