SignalR – the right way
It has been quite sometime that SignalR has been around, 2014, so why are not more people using it? First what is SignalR?
ASP.NET SignalR is a library for ASP.NET developers that makes developing real-time web functionality easy. SignalR allows bi-directional communication between server and client. Servers can now push content to connected clients instantly as it becomes available. SignalR supports Web Sockets and falls back to other compatible techniques for older browsers. SignalR includes APIs for connection management (for instance, connect and disconnect events), grouping connections, and authorisation.
For further information check https://www.asp.net/signalr
Could it because people just don’t get it or really understand what it can do, or perhaps they hit issues without realising they don’t understand the structure? Whatever the reason people are not using SignalR, I’m going to provide a useful sample application to get you off on the right footing.
There are a lot of different samples and information on how to use SignalR, but I’m always a firm believer of KISS (Keep It Simple Stupid).
There are two primary sides to SignalR, the client side and the server hubs, here I have created an MVC application with Individual User Accounts for Authentication.
Continue reading on my blog site: