Introducing ASP.NET Core Sockets
summary
Overview of the new ASP.NET Core Sockets that become the low‑level underpinnings for SignalR with a concrete plan: a host‑agnostic endpoints API sits above pluggable transports (WebSockets, Server‑Sent Events, long‑polling and TCP), formatters that support protobuf and JSON (and custom protocols), a TypeScript client and binary support, and a demo showing three clients (JS/JSON, C#/protobuf, Lua/custom) talking to one endpoint. Removes auto‑reconnect/message replay, moves to pluggable scale‑out (Redis sample) that uses channels and by default requires sticky sessions; preview mid‑2017, targeted release end‑2017.
AI-written summary · about
chapters (10)
- 0:00Start
- 4:57More Multi Hub End Points
- 9:26Binary Data Support
- 11:22Support for Pure Websocket Clients
- 12:36Returning Results from Client Method Invocations
- 21:53Protobufs
- 23:57What Does the Endpoint Code Look like
- 39:21Tcp Transport
- 43:31Unified Api
- 1:01:06Timeline
related talks
50mReal-time Web Applications with ASP.NET Core SignalR
01h 01mThe next 5 years of ASP.NET Core
01h 01mASP.NET Core 3.0: State of the art
18mReal time messaging with Angular and ASP.NET Core SignalR
53mSignalR: To Chat and Beyond
01h 00mWhat's New in ASP.NET Core?
01h 09mBuild a Highly Performant Interservice Communication with gRPC for ASP NET Core
01h 15mWhat's Next for ASP.NET Core & Blazor