Static web pages and data don't cut it anymore. Information online is real-time and even web applications should respond to continuous changes. As SignalR has recently been introduced as a component to the ASP.NET runtime there's no better time to start building web application that respond to change. SignalR does all the heavy lifting and makes it easy to introduce into a wide range of projects, so pry your application out of the static mould and start responding to the real dynamic nature of information and changes as they occur.
7. SignalR Hosts
Host agnostic – run in asp.net or stand alone with self-host on
OWIN
Changes in 2.0 – more integration with OWIN, different hub
registrations
// no longer:RouteTable.Routes.MapHubs();
namespace MyWebApplication
{
public class Startup
{
public void Configuration(IAppBuilder app)
{
app.MapSignalR();
}
}
}
8. Hubs and Connections
Connections – LOW LEVEL
Raw strings up and down
Broadcast to all clients, groups or individuals
Connection, reconnection and disconnection
semantics
Hubs – Bit higher level
Client-server and server-client
Automatic client proxy generation
23. Performance
Throughput
100,000s of message per second
Very low memory overhead
Scale
Fully async to optimise resource utilisation
1,000s of connections per server (concurrent)
Supports horizontal scaleout using pluggable message bus
backplane
24. Which are currently valid scale-out
options for SignalR?
a) SQL Server
b) Windows Azure Service Bus
c) ZeroMQ
d) Redis
e) Messaging Ferrets
http://animals.nationalgeographic.com/animals/mammals/
black-footed-ferret/
http://www.asp.net/signalr/overview/performance-and-
scaling/scaleout-in-signalr
28. Further watching
Building Real-time Applications with SignalR
http://channel9.msdn.com/Events/TechEd/NorthAmerica/201
4/DEV-B416
Microsoft ASP.NET SignalR: The Real-Time Web Made Simple
http://channel9.msdn.com/Events/TechEd/NorthAmerica/201
3/DEV-B302
Building Real-time Web Apps with ASP.NET SignalR
http://channel9.msdn.com/Events/Build/2012/3-034
