WCF Self-hosting on the client? Good or bad

Question

I wonder if anyone tried this method to get events to the client from the server side. I have an environment that uses Unix based servers and therefore cannot use WCF duplex / callbacks, etc.

The idea is that my clients are windows that run the powerful .net application, will deploy the WCF host itself and register its own host address on the server for this session. They will have a very simple contract, and the server will, when it has an update, call the client server telling it that it is waiting for it, and the client will receive it, etc.

I'm still trying to turn my head around WCF, so not sure if this is a good way to go, are there any security implications I should worry about? There are ways to make Duplex calls work on the platform.

I did something similar before using sockets, or maybe a cross-platform message queue would be the best way to do this.

thanks

76mel

Answer 1

At least it looks like this should work, although I would suggest that you could host in IIS, and since the nix servers could then just make a web call, right? I'm not sure that your own hosting will benefit you, although it should work fine, but it may be a bit of a pain in the neck to configure, etc.

, , , , , .

Answer 2

WCF . , IIS, .

, WCF , . HTTP, -, Http.sys.

Answer 3

. , . , , , , , , , , .