Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Introducing ASP.NET Core Sockets

1fe64ebb176498be5f73ab51986c6b7b?s=47 David Fowler
January 25, 2017

Introducing ASP.NET Core Sockets

1fe64ebb176498be5f73ab51986c6b7b?s=128

David Fowler

January 25, 2017
Tweet

Transcript

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

  2. It’s still very early days and everything you’re seeing here

    could and probably will change!
  3. SignalR is great, but…

  4. 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)
  5. 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
  6. 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
  7. Demos

  8. Timeline • In development right now • Preview ~mid-year •

    Release ~end-of-year • https://github.com/aspnet/signalr