Need some help/advice on WCF Per-Call Service and NServiceBus interop

I have WCF Per-Call service which provides data for clients and at the same time is integrated with NServiceBus.

All stateful objects are stored in UnityContainer which is integrated into custom service host.

NServiceBus is configured in service host and uses same container as service instances.

Every client has its own instance context(described by Juval Lowy in his book in chapter about Durable Services).

If I need to send request over bus I just use some kind of dispatcher and wait response using Thread.Sleep().Since services are per-call this is ok afaik.

But I am confused a bit about messages from bus, that service must handle and provide them to clients. For some data like stock quotes I just update some kind of stateful object and and then, when clients invoke GetQuotesData() just provide data from this object. But there are numerous service messages like new quote added and etc.

At this moment I have an idea to implement something like "Postman daemon" =)) and store this type of messages in instance context. Then client will开发者_高级运维 invoke "GetMail()", receive those messages and parse them. Problem is that NServiceBus messages are "Interface based" and I cant pass them over WCF, so I need to convert them to types derived from some abstract class.

I Don't know what is best way to handle this situation.

Have you considered a "pure" NServiceBus solution for communicating back to clients? NServiceBus already has that "Postman daemon" capability. NServiceBus messages don't have to be interfaces - you can use regular classes as well.

Hope that helps.