دانلود کتاب SignalR در NET 6 – راهنمای کامل ساده ترین راه برای فعال کردن ارتباطات دو طرفه HTTP بلادرنگ در NET 6

If you are a software developer who builds web, mobile or internet of things (IoT) applications, you will appreciate how important it is for your applications to have the ability to communicate with the server asynchronously and in real time. Also, you probably realize that the standard requestresponse model of communication isn’t fully suitable for modern apps. Sometimes, your client application (whether it’s a web page, a mobile app or a service on an IoT device) needs to be able to receive a real-time update from the server that was actually triggered by an event on the server and not by a client request. We see this functionality everywhere. When you use a messenger app, you would expect to receive a message as soon as someone has sent you one. When you control your IoT devices, you expect them to respond to your commands as soon as you trigger them. But the problem with such functionality is that the said functionality is not always easy to implement. You could still use the classic request-response model and just carry on sending requests to the server until you receive a right type of response. But this would be wasteful. And, if your client application has limited bandwidth to work with, you may not even be able to do it at all, as continuous requests to the server may end up using up the entire bandwidth really quickly. As well as all of this, your code to implement such a behavior would probably be way more complicated than it should be. There is also an alternative – WebSocket protocol. This is a much better solution. The protocol was specifically designed to enable two-way communication between the client and the server. All you have to do is establish a connection between the two endpoints. And, as long as this connection is live, the messages can flow both ways. As well as sending any arbitrary message from the client to the server, you can also send messages from the server to the client. And, on top of this, WebSocket protocol is very efficient. Maintaining the connection doesn’t use much bandwidth at all.