This post is in continuation of my previous post where we discussed the needs, basics, configurations and transport mechanism of SignalR. In this post we will take this a step further by creating a sample application and analyze it further. Broadly, this post can be divided into two major parts: In the first part, we will be creating a sample and in the other, we will see how SignalR works in various environments and look into the communication request between client and server… Read complete post on Infragistics blog
HTTP protocol is the basis for all communication over the web, and it has catered to our needs since the early days. HTTP works in a request and response model, where a request needs to be sent to the server to get any update from there. This creates challenges in handling a few scenarios where we need real time data: when a user opens a web page then it needs to be updated, and when there is a change on the server but as per the HTTP architecture, a new request must be sent to get an update from the server. This creates a bad experience for the user and multiple requests may throttle…Read complete post on Infragistics blog.
Hope you guys are doing well. You all have chance to learn various technology from Technical experts absolutely free in Lunch Time Sessions. What is Lunch Time session
“Lunch Time is a new talk series scheduled for every alternate Wednesday exactly during the Lunch Time. And the presenters of this talk series are the Most Valuable Professionals. This would give the audience a good platform to learn from these exceptional technical leaders and give product feedback to Microsoft through them.”
This is second post in the series on ASP.NET SignalR. You can access first post from the following link
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.