pollingduplexhttpbinding

I am currently working on a WCF service and have a small issue. The service is a Polling Duplex service. I initiate data transfer through a message sent to the server. Then the server sends large packets of data back through the callback channel to the client fairly quickly. To stop the I send a message to the sever telling it do stop. Then it sends a message over the callback channel acknowledging this to let the client know. The problem is that a bunch of packets of data get buffered up to be sent through the callback channel to the client. This causes a long wait for the acknowledgement to

I have followed Tomek Janczuk's Pub/sub sample using HTTP polling duplex WCF channel but I've noticed that when a client disconnects by closing the browser the service does not notice on the next callback. I would have expected an exception or something to say that the endpoint was not there any longer. How can you know when a client is gone, so as to stop publishing to that client? It seems there's one unsatisfactory, albeit simple solution: If the client callback times out, don't call it again. In my system I've also implemented a manual "check" call - every n seconds the server calls a

I have WCF service. Here is configuration <basicHttpBinding> <binding name="EmergencyRegistratorBinding"> <security mode="TransportCredentialOnly"> <transport clientCredentialType="Windows" /> </security> </binding> </basicHttpBinding> And service configuration <service behaviorConfiguration="Default" name="Breeze.AppServer.Emergencies.EmergencyRegistrator"> <endpoint address="" binding="basicHttpBinding" bindingConfiguration="EmergencyRegistratorBinding" contract="Services.IEmergencyRegistrator" /> </service> Everything worked fine. But I needed to change basicHttpBingind to DuplexBinding. I

Eventually WCF duplex Silverlight 4 client start getting 404 Not Found errors for poll messages, immediately after poll was send from WCF service to Silverlight client, sometimes this happens for second poll sometimes connectivity works hours or even days, but mostly fails on first minutes. ! And what is interesting the issue is like known Silverlight 4 bug when using MaxMessagesPerPoll duplex mode and solution is described here and here but I'm using SingleMessagePerPoll mode. ANyway I tried using ClientStack as suggested but nothing changed. General flow: SL client executes WCF service