SignalR for .net and observer pattern

So far I have looked through many articles explaining SignalR.

The search leads to a simple definition: SignalR can be used to develop a real-time web application.

According to the wiki: a real-time web application is a set of technologies and methods that allow users to receive information as soon as they are published by its authors, and do not require that they or their software periodically check the source for updates.

SignalR seems to be similar to the observer / publisher and Subscriber pattern, where the client subscribes to the server and the server sends a notification to all the client if an event occurs.

So my query is: 1) Is this SignalR based on the messaging pattern (i.e. watcher / publisher and subscriber)?

2) If yes, then why is there another SignalR messaging template when we already have an existing one.

3) What are the benefits of SignalR over the messaging template (watcher / publisher and subscriber)

+3
source share
1 answer

Almost 4 years did not answer this question! SignalR is Microsoft's recommended real-time application development solution. The Http request / response model requires the client to call the server to receive a response from the server. But SignalR allows the server to send messages to clients without the participation of the client, often polling the server.

Answer1. , /. . ( ) .

2 3.. , (, fb, eventlog ..), . TechNet- , SignalR, .

Stock Market , . - - .

+4

All Articles