Web e device in real time con asp.net Signal R
Download as PPTX, PDF0 likes576 views
This document discusses SignalR, an ASP.NET library for adding real-time web functionality to applications. It allows for persistent connections and calling methods between client and server. SignalR supports WebSockets and fallback techniques. The document covers SignalR components, its two-level API using Hubs and PersistentConnections, JavaScript client generation, and performance considerations like message size and configuration settings.
More Related Content
What's hot (20)
Viewers also liked (20)
Similar to Web e device in real time con asp.net Signal R (20)
Recently uploaded (20)
Web e device in real time con asp.net Signal R
- 1. Web e device in real time con ASP.NET SignalR Giuseppe Marchi Microsoft MVP SharePoint Luca Zulian MCTS ASP.NET 4
- 2. What is SignalR? Under the Hood Building Apps with SignalR SignalR outside .NET Framework _1 _3 _5 _18 Performance & testing _21
- 3. What is SignalR for Developers? • A library for ASP.NET developers that simplifies the process of adding real-time functionality • An Open Source library (github.com/SignalR/SignalR) • Well Documented library (asp.net/signalr) • Always up to date
- 4. What SignalR offers to Developers • Real-time, persistent connection abstraction over HTTP for .NET (supports Web Sockets, and falls back to other compatible techniques for older browsers) • Simplicity • Reach • Performance • Scalability • Security • Extensibility
- 5. SignalR: under the hood
- 6. Before Start: Components • Meta Package (Microsoft.AspNet.SignalR) • Core (Microsoft.AspNet.SignalR.Core) • Hosts (Microsoft.AspNet.SignalR.SystemWeb, Microsoft.AspNet.SignalR.Owin) • Clients (Microsoft.AspNet.SignalR.Js, Microsoft.AspNet.SignalR.Client) • Scaleout Buses (Microsoft.AspNet.SignalR.Redis, Microsoft.AspNet.SignalR.ServiceBus)
- 7. DEMO
- 8. Simplicity: two level API Choose the level of abstraction that works for you
- 9. Two level API: Configuration Remember: call RouteTable.Routes.MapHubs() as the first line of code in the Application_Start method, this must be called before you register any other routes.
- 10. Two level API: Hub Configuration Remember: call RouteTable.Routes.MapConnection() as the first line of code in the Application_Start method, this must be called before you register any other routes.
- 11. Two level API: PersistentConnection • Low-level • Simple endpoint for sending single-recipient, grouped, or broadcast messages • Gives direct access to the low- level communication protocols • PersistentConnection class • Connect, reconnect & disconnect semantics
- 12. Two level API: PersistentConnection PersistentConnection API
- 13. Two level API: PersistentConnection
- 14. DEMO
- 15. Two level API: Hub • More high-level pipeline • Allows your client and server to call methods each other directly (internal routing) • Allows you to pass strongly typed parameters to methods, enabling model binding • Hub class • Automatic client proxy generation (Javascript)
- 16. Two level API: Hub Hub API
- 17. Two level API: Hub
- 18. DEMO
- 19. Simplicity: Javascript client • Javascript proxy (AUTOMATICALLY created on ~/signalr/hubs)
- 20. Simplicity: Windows8 & WP8 client • Microsoft.AspNet.SignalR.Client • Hub • PersistentConnection
- 21. Transport Negotiation SignalR isolates us from low-level details, giving us the impression of working on a permanently open persistent connection
- 22. But isn’t real-time web just chat? • Dashboards & monitoring • Collaborative anything • Job progress • Real-time forms • Gaming • …
- 23. SignalR outside .NET framework • SignalR-ObjC - Native for iOS clients • SignalA - Native for Android clients • Xamarin (in xamarin branch https://github.com/SignalR/SignalR/tree/xamarin, but need some tricks)
- 24. SignalR on IIS? Supported server operating systems • Windows Server 2012 • Windows Server 2008 r2. • Windows 8 • Windows 7 • Windows Azure Supported .NET Framework versions • SignalR is supported on both .NET Framework version 4 and 4.5. For WebSockets to be supported, .NET Framework 4.5 must be used. Supported IIS versions • IIS 8 or IIS 8 Express • IIS 7 and 7.5. Support for extensionless URLs is required • IIS must be running in integrated mode; classic mode is not supported • The hosting application must be running in full trust mode
- 25. SignalR only on IIS? • Console Applications, Windows Services (Microsoft.AspNet.SignalR.SelfHost) • OWIN (Microsoft.AspNet.SignalR.Owin) • Mono
- 26. SignalR performance & testing • SignalR Crank or Stress projects from repository • Performance Monitor (Perfmon.exe)
- 27. SignalR performance & testing • Connections Connected • Connections Reconnected • Connections Disonnected • Connections Current • Connection Messages Received Total • Connection Messages Sent Total • Connection Messages Received/Sec • Connection Messages Sent/Sec SignalR Performance Counter
- 28. SignalR performance considerations Reducing message size • JsonIgnore attribute • JsonProperty attribute to reduce message size Modify SignalR configuration settings • DefaultMessageBufferSize Modify ASP.NET configuration settings • Maximum concurrent requests per CPU • Request Queue Limit Modify IIS configuration settings • Max concurrent requests per application
- 29. Q&A
- 30. Contatti OverNet Education • TEL. +39 02 365738 • EMAIL info@wpc2013.it • WEB www.WPC2013.it • TWITTER @Overnete
- 31. Thank You