- Still very early days so much of this could change
- Architecture diagram: Sockets vs. SignalR
- SignalR Core new features
- non-HTTP
- Binary support
- Endpoint API & formatters
- Custom protocols
- No-jQuery dependency (works in Web Workers & Node.JS now)
- Pure WebSocket client
- Get results from client invocations
- Endpoint API
- Endpoints
- Connections
- Channels
- Reading messages
- Adapting to a stream/pipeline
- Using Formatters to send/receive typed messages
- Using ConnectionList to track connections
- Connection lifetime
- SignalR
- Hubs
- Proxies
- Scale-out design & changes
- Differences
- Stick-sessions required
- No global ordering by default
- No reconnect except for Long Polling
- Less opinionated thus more flexible
- DEMOS:
- Multi-transport chat via Endpoints
- Multi-protocol Social Weather using Endpoints & IoT
- Chat using Hubs
- Scaleout via HubLifetimeManager
- Timeline
Last active
January 18, 2017 15:49
-
-
Save DamianEdwards/a10fcf11bed4bfd07571693274334d4e to your computer and use it in GitHub Desktop.
NDC London SignalR Core
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment