Is Sockets effective for communicating with the Service?

I have a great C # / WPF application. This application should collect data from other "sub" applications that will run on a Windows service - on the same network, on another PC. Are sockets the best way to handle messages between them (unlike deleted or others)?

+4
source share
4 answers

WCF is the recommended approach for internetworking in version 3.5 and higher. Sockets and named pipes may / will work, but you will find much better support through WCF.

+5
source

In no case. Use WCF .

+5
source

I would say that this ultimately depends on your performance requirements. Look at WCF as an abstraction layer located above the sockets. The price you pay for bundle is performance, but I would be surprised if WCF did not provide you with sufficient performance.

+2
source

Sockets are the fastest thing you can get, so if you need to do it as fast as you can use sockets. They are more complicated than WCF, but in return you get full control at the lowest level.

Also, make sure that the actual bottleneck will be in serializing / deserializing the objects transferred between the client and server (of course, if they are complex).

0
source

All Articles