Your SlideShare is downloading. ×
0
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Signal rity1
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Signal rity1

572

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
572
On Slideshare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. SignalRity Yaniv Rodenski Senior Architect – Sela Group Level: Intermediate - Advanced
  • 2. The way I used to get my data
  • 3. The way She is Getting her Data
  • 4. How do I get my data?
  • 5. Real-Time Web
  • 6. SignalRity Yaniv Rodenski Senior Architect – Sela Group Level: Intermediate - Advanced
  • 7. About me: • Senior Architect - Sela Group • Windows Azure MVP • Coauthor of Developing Windows Azure and Web Services (MOC 20487)
  • 8. Evolution of the real-time web Polling Long Polling Forever-Frame Server-sent Events WebSockets
  • 9. Demo Using WebSockets
  • 10. Why WebSockets are not Enough? • HTML5 standard – great if you are living in 2020 • Low-level API • Strict prerequisites
  • 11. Introducing SignalR • Rich API for real-time web applications • Supports WebSockets • Fallback to other mechanisms
  • 12. Hubs • Hubs are high-level SignalR APIs • Provide a service-like abstraction • Provide a mechanism for invoking client methods
  • 13. Demo Hello Hubs
  • 14. Targeting Specific Clients • When a client calls a hub, it gets a connection id • You can use this connection id to send a message to this specific client Clients.Client(connectionId).sendMessage(message)
  • 15. Groups • Clients can be registered with a group • Part of the Hubs API Groups.Add(Context.ConnectionId, groupName); Clients.Group(groupName).invokeSomeClientMethod(args…);
  • 16. Demo Clients and Groups
  • 17. Scaling out with SignalR • One of the biggest issues with the “real- time web” is scaling out • SignalR can span across multiple hosts using either Redis, SQL Server or Windows Azure Service Bus
  • 18. Demo Scaling out with Windows Azure
  • 19. SignalR .NET Clients • You can create SignalR clients in any .NET environment – .NET applications – Windows 8, Windows Phone 8 Apps – Even Silverlight – Xamarin
  • 20. Demo A .NET Client
  • 21. Summary • Real-time web does not need to be painful • SignalR can let you use the best available option • SignalR is not just for web clients • SignalR scales
  • 22. Resources • http://signalr.net/ • Twitter: @DamianEdwards, @davidfowl • http://sdrv.ms/152qU0b • @YRodenski

×