Tweet
Tweet

Slide 1

Slide 1 text

Introducing ASP.NET Core Sockets (SignalR reimagined) @damianedwards @davidfowl

Slide 2

Slide 2 text

It’s still very early days and everything you’re seeing here could and probably will change!

Slide 3

Slide 3 text

SignalR is great, but…

Slide 4

Slide 4 text

Some things need to change • No more jQuery dependency (yay!) • No more auto-reconnect with message replay • No more Hub-state • No more multi-hub endpoints • No more single-model scale-out • No more multi-server ping-pong (now require sticky sessions)

Slide 5

Slide 5 text

New for ASP.NET Core SignalR • Binary data support, e.g. send/receive binary data • Host-agnostic (enables non-HTTP transports) • All-new connection-level “Endpoints” API • Multiple protocols/formats support, e.g. JSON, ProtoBuf, custom • Support “pure” WebSocket clients • Return results from client method invocations • TypeScript client • Flexible scale-out extensibility

Slide 6

Slide 6 text

Host Transports Endpoints Hubs Middleware HTTP Transports HubEndpoint Hubs WebHost WebSockets ServerSentEvents Long Polling Formatters TcpServer TcpTransport ASP.NET Core Sockets Architecture ASP.NET Core SignalR on Sockets

Slide 7

Slide 7 text

Demos

Slide 8

Slide 8 text

Timeline • In development right now • Preview ~mid-year • Release ~end-of-year • https://github.com/aspnet/signalr