This is second post in the series on ASP.NET SignalR. You can access first post from the following link
Learning ASP.NET SignalR – Part 1
In this post, we’ll examine, How SignalR works on various environments. We’ll try dig it out with the help of an example.
First let me know, when you require real time update your UI?
A chat application?
Right. But it’s not the chat application only, you can use it at many other scenarios like any real time data requirement, collaborative applications, Real time loggers, Real Time dashboards, Games, Stock market, Real time news, Live match feeds etc… and many more.
But for this analysis, we’ll use chat application. And will discuss other scenarios in my next post.
Today I am going to discuss one of the new technologies that changed the way we used to think about How the web works. I’ll be writing a series on this technology and this post is first part of it.
You must have been working on the ASP.NET for long or might be since inception. And till date (or till this technology got introduced) , You got to know from every where that Web is stateless. A webpage is recreated every time from scratch it is posted back to server. In traditional web programming, all the information within the page and control gets wiped off on every postback.
I have taken the above lines from one of my post which I had written long back.