We have been using PollingDuplexHttpBinding
for some time to do Pub/Sub
messaging. We have methods that do not return results that allow clients to subscribe to some data feed then then the service pushes data back via CallBack
contracts.
Just now we have been adding some Request/Reply
methods to our OperationContract
. As the clients are Silverlight 3 these methods are called using the async Begin() End()
pattern. The problem is we cannot get this to work using PollingDuplexHttpBinding
. We always get the following error (when client stack HTTP is used):
The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.
With browser stack we get HTTP 500: Not Found.
When switching to BasicHttpBinding
the Request/Reply
methods are called completely fine, but obviously Pub/Sub
methods cannot be used with this binding.
We could use two seperate endpoints for each type of messaging, but would rather not and it seems odd to me that a binding would only support the Pub/Sub
pattern (even though this is the motivation for PollingDuplexHttpBinding
).
Could someone clear this up for me? Is it possible?