Nayyeri Keyvan - Pro ASP.NET SignalR Real-Time Communication in .NET with SignalR 2.1
Here you can read online Nayyeri Keyvan - Pro ASP.NET SignalR Real-Time Communication in .NET with SignalR 2.1 full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. City: Berkeley;CA, year: 2014, publisher: Apress, Imprint, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
- Book:Pro ASP.NET SignalR Real-Time Communication in .NET with SignalR 2.1
- Author:
- Publisher:Apress, Imprint
- Genre:
- Year:2014
- City:Berkeley;CA
- Rating:4 / 5
- Favourites:Add to favourites
- Your mark:
Pro ASP.NET SignalR Real-Time Communication in .NET with SignalR 2.1: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "Pro ASP.NET SignalR Real-Time Communication in .NET with SignalR 2.1" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
ASP.NET SignalR is the new solution to real-time communication between servers and clients in .NET. Use it to push new data to a web page or mobile device as soon as it becomes available, whether its a notification, live chat, up-to-the-minute financial data, or a range of other exciting applications. Innovations like Google live search and live Facebook and Twitter updates are pushing users expectations of the real-time web. With Pro ASP.NET SignalR, you can join this revolution and learn skills that will be valuable for years to come. Pro ASP.NET SignalR starts with an introduction to the real-time web. Learn about the technologies underlying the SignalR library, such as WebSockets and long-polling, and how SignalR elegantly flips between them depending on the capabilities of the client. Next, meet the concepts of hubs and persistent connections and how to use them to build the components of an ASP.NET SignalR application. Find out how to extend, test, debug, configure, scale, and host your applications, and how to target a range of clients, including Windows and iOS. The book rounds off with two case studies-a stock market price updater, and a collaborative drawing application-so you can get to grips with SignalR in a realistic scenario, using a broad range of the concepts covered in earlier chapters. As real-time updates to web and mobile apps become the norm, Pro ASP.NET SignalR will be your in-depth, one-stop companion to this new and exciting technology.
Nayyeri Keyvan: author's other books
Who wrote Pro ASP.NET SignalR Real-Time Communication in .NET with SignalR 2.1? Find out the surname, the name of the author of the book and a list of all author's works by series.
Peter Himschoot
Jose M. Aguilar
Einar Ingebrigtsen
Andy Meadows
Pro ASP.NET SignalR Real-Time Communication in .NET with SignalR 2.1 — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Pro ASP.NET SignalR Real-Time Communication in .NET with SignalR 2.1" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Light
Font size:
↓
↑
Reset
Interval:
↓
↑
Bookmark:
Make
Keyvan Nayyeri 2014
Keyvan Nayyeri and Darren White Pro ASP.NET SignalR 10.1007/978-1-4302-6320-3_11. Introduction to the Real-Time Web and ASP.NET SignalR
Keyvan Nayyeri 1
(1)
TX, United States
The Internet is one of the most important inventions in history, and it has changed our lives for the better in many ways. For social creatures such as humans, nothing could be better than a fast method of communication with the world that enables multimedia content delivery with almost no delay.
In its few decades of existence, the Internet has evolved from a basic set of network clusters with simple operations to the foundation of almost everything in our world, providing opportunities to make billions of dollars.
Our mission in this book is to walk you (and other Microsoft web developers with a good background in ASP.NET and JavaScript) through a very recent technology called ASP.NET SignalR. It enables the creation of real-time, asynchronous web applications that are the most modern type of infrastructure for building sites to deliver content from servers to clients in real time and remove any latency. Clients sit on a page on your site and receive the newest updates in real time with no need to click anything or refresh the page. For example, on Facebook when somebody leaves a comment or likes one of your photos, you do not need to refresh the page to see the notification pop up and the red counter being updated. ASP.NET SignalR provides the foundation to develop such features.
This chapter gives you some background information on SignalR and how it can help you build modern web sites. The following are the major topics covered in this chapter:
- How the Internet has evolved to where it is today
- Why client-side experience is more important than ever
- Definition of realtime web application development
- Some examples of realtime web application development
- Historical overview of ASP.NET SignalR
- Introduction to ASP.NET SignalR and some of its characteristics
- ASP.NET SignalR architecture
- Overview of different transport options in ASP.NET SignalR
- Main challenges for realtime web development
Evolution of the Internet
The Internet started as a simple set of clusters with some computers connected to perform basic operations. It quickly became a very sophisticated network of servers all around the world that serve hundreds of millions (even billions) of clients.
There have been different kinds of changes on this worldwide network in different domains. In one area, Internet connections became faster and more reliable, enabling users to download and upload larger content so that it is now possible for users to download and upload highquality multimedia content (e.g., videos) from their mobile Internet connections. It has also opened new doors for content providers and consumers.
In another area, Internet browsers evolved to be very sophisticated, and enabled features to facilitate the creation and delivery of content in more user-friendly ways. For at least a decade, the use of Asynchronous JavaScript and XML (AJAX) technologies has given a smoother user experience to end users, for example.
In a third area, server technologies have evolved to also accommodate browser and connection advancements. New programming languages and platforms have been introduced, along with many libraries that help simplify the process of web application creation for web developers. One of these recent advancements is the support for WebSockets.
All the different trends on the Internet focused on providing a better user experience. We have moved from serving static HTML web pages to dynamic pages that can be updated based on users actions. We can then use client-side languages (mostly JavaScript) to process certain things on the browser and reduce the need to refresh a web page to get the new content. Currently, there is a more modern approach: real-time delivery of content from servers to clients that is possible by applying server-side technologies in conjunction with JavaScript. This is the area in which SignalR comes into play.
Why the Client-Side Experience Is More Important than Ever
The concept of user has become the most important concept in todays Internet. Almost all businesses, regardless of their size, know how important the user experience can be. They have moved their focus to making products, technologies, and software that is intuitive and simple enough to attract almost any user regardless of age, gender, cultural background, and so on.
An important part of the user experience is the speed of delivering content. Traditionally, the Internet was a set of web pages served on servers and received by clients. These pages included many static pages that could not react dynamically to users actions and dynamic pages that could render a dynamic content based on the inputs provided by users. Users had to send their actions to servers or request a particular Uniform Resource Locator (URL) from the server to receive HTML content. This was a very simple model and lacked the sophistication seen in modern web sites.
As the user experience became more important, web designers and developers came up with the idea of using JavaScript and XML in conjunction with partial content rendering on the servers to take advantage of the concept of AJAX. It would provide a smoother experience to users and deliver content to these users more quickly.
In the past few years, however, this approach wasnt good enough for the modern needs of the Internet. Even with AJAX, there was often a wait for users actions to update a portion of the page and deliver the content, so the speed of content delivery was very dependent on the speed of the users interactions.
This issue led web developers and designers to start thinking about sending the content from servers to clients as it arrives in real time, or at least invent mechanisms that simulate such a behavior. This process is called realtime web application development .
RealTime Web Application Development
The term real-time software refers to the type of software that is subject to a soft or hard time constraint. By the nature of its business domain, this type of software must complete its processing within a particular timeframe. This time constraint can be strict to make it hard real-time software or flexible to make it soft real-time software. For example, aerospace software can be hard real-time software because it must finish its execution within a defined time interval; otherwise, operations might fail, and peoples lives can be in danger. In contrast, video players can be soft real-time software because it is not mission-critical if the processing does not finish on time (although it is important to process the videos in time to display them to users).
Although real-time software and real-time computing have been around for a long time, the term real-time web is relatively new. This concept, which was introduced in the past few years, focuses on real-time delivery of content to clients as soon as it is available.
The real-time web is similar to soft real-time software because the delivery of content from the information source to consumers should occur in a short period of time to be considered real time (from a few milliseconds up to 1 second).
The real-time web was embraced by social networks and their need to update users with frequent status updates and content changes by friends and peers. Facebook and Twitter were among the first major sites on the Internet that pioneered in this area and implemented real-time web features.
Light
Font size:
↓
↑
Reset
Interval:
↓
↑
Bookmark:
Make
Similar books «Pro ASP.NET SignalR Real-Time Communication in .NET with SignalR 2.1»
Look at similar books to Pro ASP.NET SignalR Real-Time Communication in .NET with SignalR 2.1. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Peter Himschoot
Jose M. Aguilar
Einar Ingebrigtsen
Andy Meadows
Reviews about «Pro ASP.NET SignalR Real-Time Communication in .NET with SignalR 2.1»
Discussion, reviews of the book Pro ASP.NET SignalR Real-Time Communication in .NET with SignalR 2.1 and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.