rhlbhl

Hi,

I have an application architecture in which I have one WCF service and multiple .net applications on same machine. Since everything resides on same machine I'm using namedPipeTcp. .Net application/s calls the WCF service and WCF service stores the callback channel of each application in it, since it (WCF service) might need to call .Net application's side method later. Its a duplex channel mechanism. But the scenario is not Actually a async operation where request is made to WCF service and reply it sent back after some time.
it is just that WCF service stores the callback channel of each application and whenever it wants to send any other message to .net client it uses the stored callback. Everything works great!!!

Instead of this architecture, we have another option..that, have one WCF service and each .net application will again host its own WCF service.. So whenever, main WCF wants to send message to .Net application it will actually send message to WCF service residing in that application.

Can you please let me know advantages/disadavantgs of both of these approaches?

Thanks
Rahul