Real-time Communication with SignalR and Cloud
•Download as PPTX, PDF•
0 likes•520 views
This document discusses using SignalR to enable real-time communication between clients and servers. SignalR allows for bidirectional communication through features like hubs and persistent connections. It works across browsers and devices by using techniques like websockets, server-sent events, and long polling. SignalR provides security through connection tokens and supports performance at scale through backplanes like Azure Service Bus. In conclusion, SignalR is a library that enables real-time applications by facilitating client-to-server and server-to-client communication with broadcasting capabilities and low latency.
![{
“name” : “Radu Vunvulea,
“company” : “iQuest”,
“userType” : “enthusiastic”
“technologies” : [ “.NET”, “JS”, “Azure”, “Web”,
“Mobile”, “SL” ],
“blog” : “vunvulearadu.blogspot.com”,
“email” : ”vunvulear@gmail.com”,
“socialMedia” :
{
“twitter” : “@RaduVunvulea”,
“fb” : “radu.vunvulea”
}
}
Who am I?](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Real-time Communication with SignalR and Cloud
Similar to Real-time Communication with SignalR and Cloud (20)
Recently uploaded
Recently uploaded (20)
Real-time Communication with SignalR and Cloud
- 1. Real-time fluent communication using SignalR and Cloud Radu Vunvulea vunvulear@gmail.com http://vunvulearadu.blogspot.com
- 2. { “name” : “Radu Vunvulea, “company” : “iQuest”, “userType” : “enthusiastic” “technologies” : [ “.NET”, “JS”, “Azure”, “Web”, “Mobile”, “SL” ], “blog” : “vunvulearadu.blogspot.com”, “email” : ”vunvulear@gmail.com”, “socialMedia” : { “twitter” : “@RaduVunvulea”, “fb” : “radu.vunvulea” } } Who am I?
- 3. Agenda • What? • When? • Where? • How? • Why?
- 7. •Static Web • HTML & Request/Response •Ajax • jQuery & Prototype •Real Time Web • Real Time Libraries & Web Socket
- 8. Real Time Interaction • Chat • Notifications • Weather • Stock market • Auction • Games • Monitoring • Dashboard • Document editing
- 9. • WebSocket • Forever Frame • Server Sent Events • Pooling • SPDY What we can use?
- 10. What we can use? • Commet • Pusher • SockJS • SocketIO • Faye • Now.js • Sse • Django-sse • Cramp
- 11. What we can use? • Commet • Pusher • SockJS • SocketIO • Faye • Now.js • Sse • Django-sse • Cramp SignalR
- 12. What is SignalR? • Async library for .NET to help build real-time, multiuser interactive web applications • Bidirectional communication • Open Source • Adopted by Microsoft • GitHub
- 13. When we can use it? • Server • Windows (.NET) • Mono • Clients • Chrome • Firefox • Safari • IE • Opera • Android browser • IoS • Windows Desktop • Silverlight • Windows Store • Windows Phone • and old browsers
- 14. Connection methods • WebSocket • Server Side Events • Forever Frame • Ajax long pooling
- 15. Persistent Connection • Similar with WebSocket • Persistent • Events • Connect • Disconnect • Receive • Error • Methods • Send • Broadcast
- 16. Hubs • Over Connections • Share variables • Calls between client and server • Serialization • Capture connect/disconnect • Everything works by magic
- 17. Hubs • When you have multiple hubs • Same connection is shared by a client • Groups are maintain separately for each hub • One proxy JS file for all hubs • Async support • OnConnected • OnDisconnected • OnReconnected • proxy.State (JS) & Client.Caller (C#)
- 19. Hubs vs Persistent Connections Hubs • Remote invocation Persistent Connections • Message format needs to be specified • Messaging and dispatching model • An existing app is ported to SignalR
- 20. Security • Based on Connection Token (Connection Id + Username) • Unique • Managed by server • Encrypted with a digital signature • Connection Id • Exist until the end of connection • Username • Only for authenticated users • Passed between client and server for each request
- 23. CSRF and SignalR • Disable cross domain requests • Verify connection token • Put connection token query string • The connection token is not persisted on the client
- 24. Performance • Single Box • Over 450.000 messages per second • 15.000 – 20.000 connection (hardware limitations – ports) • Web farm • You have “NO” limit • You need to synchronize each node from the farm
- 28. SignalR Farm • Backplanes: • Windows Azure Service Bus • Redis • SQLServer • Server broadcast • High-frequency realtime • Client to client
- 30. Conclusion • SignalR • Client to Server • Server to Client • Broadcasting • Real Time application • Scalable • Low latency
- 31. Question Answers