- •Contents at a Glance
- •Introduction
- •Who should read this book
- •Assumptions
- •Who should not read this book
- •Organization of this book
- •Finding your best starting point in this book
- •Conventions and features in this book
- •System requirements
- •Code samples
- •Notes on the version
- •Installing the code samples
- •Using the code samples
- •Acknowledgments
- •Errata & book support
- •We want to hear from you
- •Stay in touch
- •HTTP operations
- •Polling: The answer?
- •Push: The server takes the initiative
- •WebSockets
- •Server-Sent Events (API Event Source)
- •Push today
- •The world needs more than just push
- •What does SignalR offer?
- •Two levels of abstraction
- •Supported platforms
- •OWIN and Katana: The new kids on the block
- •Installing SignalR
- •Implementation on the server side
- •Mapping and configuring persistent connections
- •Events of a persistent connection
- •Sending messages to clients
- •Asynchronous event processing
- •Connection groups
- •The OWIN startup class
- •Implementation on the client side
- •Initiating the connection by using the JavaScript client
- •Support for older browsers
- •Support for cross-domain connections
- •Sending messages
- •Receiving messages
- •Sending additional information to the server
- •Other events available at the client
- •Transport negotiation
- •Adjusting SignalR configuration parameters
- •Complete example: Tracking visitors
- •Project creation and setup
- •Implementation on the client side
- •Implementation on the server side
- •Server implementation
- •Hub registration and configuration
- •Creating hubs
- •Receiving messages
- •Sending messages to clients
- •Sending messages to specific users
- •State maintenance
- •Accessing information about the request context
- •Notification of connections and disconnections
- •Managing groups
- •Maintaining state at the server
- •Client implementation
- •JavaScript clients
- •Generating the proxy
- •Manual generation of JavaScript proxies
- •Establishing the connection
- •Sending messages to the server
- •Sending additional information
- •Receiving messages sent from the server
- •Logging
- •State maintenance
- •Implementing the client without a proxy
- •Complete example: Shared drawing board
- •Project creation and setup
- •Implementation on the client side
- •Implementation on the server side
- •Access from other threads
- •External access using persistent connections
- •Complete example: Monitoring connections at the server
- •Project creation and setup
- •Implementing the website
- •System for tracing requests (server side)
- •System for tracing requests (client side)
- •External access using hubs
- •Complete example: Progress bar
- •Project creation and setup
- •Implementation on the client side
- •Implementation on the server side
- •Multiplatform SignalR servers
- •SignalR hosting in non-web applications
- •SignalR hosting in platforms other than Windows
- •Multiplatform SignalR clients
- •Accessing services from .NET non-web clients
- •Consumption of services from other platforms
- •Growing pains
- •Scalability in SignalR
- •Scaling on backplanes
- •Windows Azure Service Bus
- •SQL Server
- •Redis
- •Custom backplanes
- •Improving performance in SignalR services
- •Server configuration
- •Monitoring performance
- •Authorization in SignalR
- •Access control in persistent connections
- •Access control in hubs
- •Client authentication
- •An extensible framework
- •Dependency Injection
- •Manual dependency injection
- •Releasing dependencies
- •Inversion of Control containers
- •Unit testing with SignalR
- •Unit testing of hubs
- •Unit testing persistent connections
- •Intercepting messages in hubs
- •Integration with other frameworks
- •Knockout
- •AngularJS
- •Index
- •About the author
#result p {
margin: 0 0 10px 0;
}
Script (Scripts/ProgressBar.js)
$(function () {
var hub = $.connection.progressBarHub; hub.client.update = function (value) {
$("#progressBar").css("width", value + "%")
.text(value + " %");
};
$("#start").click(function () { $(this).attr("disabled", true); $("#result")
.hide("slow")
.load("hardprocess.aspx?connId=" + $.connection.hub.id, function () {
$(this).slideDown("slow"); $("#start").attr("disabled", false);
});
});
$.connection.hub.start()
.done(function () { $("#start").attr("disabled", false);
});
});
Implementation on the server side
Hub
using Microsoft.AspNet.SignalR;
namespace ProgressBar
{
public class ProgressBarHub : Hub { }
}
Note that we do not need any method in the hub, because the information is sent to the clients through the external process, as shown in the following code example.
Expensive process (HardProcess.Aspx)
<%@ Page Language="C#"
Inherits="System.Web.UI.Page" EnableSessionState="false" %> <%@ Import Namespace="System.Diagnostics" %>
<%@ Import Namespace="System.Threading" %>
<%@ Import Namespace="Microsoft.AspNet.SignalR" %> <%@ Import Namespace="ProgressBar" %>
<%
Persistent connections and hubs from other threads Chapter 6 |
115 |
www.it-ebooks.info
Response.Expires = -1;
var connectionId = Request["connId"]; var hub = GlobalHost.ConnectionManager
.GetHubContext<ProgressBarHub>(); Stopwatch stopWatch = Stopwatch.StartNew();
// Simulate a very very hard process...
for (int i = 1; i <= 100; i++)
{
hub.Clients.Client(connectionId).update(i); Thread.Sleep(150);
}
%>
<p>The answer to life, the universe and everything is: 42.</p> <p>
And it only took <%:stopWatch.ElapsedMilliseconds / 1000 %> seconds to find it out.
</p>
This page receives the connection identifier as a parameter, which allows it to send the progress data only to the specific client that initiated the process.
Startup code (startup.cs)
using Owin;
public class Startup
{
public void Configuration(IAppBuilder app)
{
app.MapSignalR();
}
}
116 Chapter 6 Persistent connections and hubs from other threads
www.it-ebooks.info