What is the best way to communicate between a WCF service and individual threads?

The wording of the question does not necessarily make the problem of justice ...

  • I have a client user interface sitting in a local field and a background window service to support it when it performs background functions.
  • The client user interface is only the presentation layer, and the Windows service performs all the tough actions ... so there is a connection between them. After spending some time at Google and reading the best practices, I decided to create a service level using WCF and named pipes.
  • The client client interface is a WCF client, and the Windows service acts as a WCF host (only locally local) to support the client.

So it works just as it should. The client user interface can transfer data to the WCF host. But my question is: how do I make this data useful? I have several engines running on a Windows / WCF host, but the WCF host is completely unaware of the existence of any background engines. I need client communication requests to be able to interact with these engines.

Does anyone have an idea of ​​a good design template or methodology on how to approach facilitating communication between a WCF host and current streams?

+5
source share
1 answer

, , / WCF.

, , , wcf , , , . ( WCF) .

, , WCF, WCF .

, , , , /, .

( ), .

, WCF , - . WCF, , , , .

:

1) , , / .

2) .

3) WCF , (, , , ..).

:

, , , . , , WCF , , .

, .

+3

All Articles