Download as PPSX, PPTX
![CLIENT
SERVER
Traditional Web Approach
Sends a Request to the Server – (Step 1)
[In other words, the Client is trying to
pull some information from the Server]
Processes
the Request
(Step 2)
Response Sent back to the Client – (Step 3)](https://image.slidesharecdn.com/signalr1-150502131940-conversion-gate01/75/SignalR-With-ASP-Net-part1-4-2048.jpg)
![CLIENT
SERVER
Traditional Web Approach
Sends a Request to the Server – (Step 1)
[In other words, the Client is trying to
pull some information from the Server]
Processes
the Request
(Step 2)
Response Sent back to the Client – (Step 3)](https://crownmelresort.com/image.slidesharecdn.com/signalr1-150502131940-conversion-gate01/75/SignalR-With-ASP-Net-part1-4-2048.jpg)
Uploaded byEsraa Ammar
SignalR With ASP.Net part1
This document provides an overview of traditional web approaches, real-time web applications, and SignalR. It discusses how traditional approaches rely on pulling data via HTTP requests, while real-time approaches use pushing via persistent connections. SignalR is introduced as a library that abstracts different transport mechanisms and allows developers to focus on application logic rather than connection handling. Key concepts covered include SignalR transports, connections, hubs for server-client communication, and how to get started with SignalR. The document concludes with a note about an upcoming demo.
More Related Content
Similar to SignalR With ASP.Net part1
SignalR With ASP.Net part1
- 2. Topics Focused On!!! •Traditional Web Approach – Traditional Web Approach – Issues • What does “Real Time” mean? • SignalR – Types of Transports – Types of Connections • How do I get SignalR? • Demo
- 3.
- 4. CLIENT SERVER Traditional Web Approach Sendsa Request to the Server – (Step 1) [In other words, the Client is trying to pull some information from the Server] Processes the Request (Step 2) Response Sent back to the Client – (Step 3)
- 5. • Not Persistentconnection – Issues Each time re-established for each communication. • Http Request – Issues
- 6. Real Time WebApplications
- 7. What is RealTime Web Application? • “Real Time” means an immediate response being sent by the Server to the Client. • Real Time is “Pushing” instead of “Pulling” • Push Technology is completely different from Pull Technology. Its about getting told what’s new, instead of asking for what’s new!!!
- 8. CLIENT SERVER User Sendsa Request to the Server Creates a Persistent Connection between them Real Time Web Approach Response Sent back to the Client Response Sent back to the Client Response Sent back to the Client
- 9.
- 10. Long Polling Server Client Request Response Variable delay •Long polling does not create a persistent connection, but instead polls the server with a request that stays open until the server responds, at which point the connection closes, and a new connection is requested immediately.
- 11. Forever Frames • Internallycreates an Iframe along with a script on the page to fetch the data. • The server then continually sends script to the client which is immediately executed, providing a one-way realtime connection from server to client. • Supported on IE Browser.
- 12.
- 13.
- 14. Server Sent Events •Requires a single connection between Client-Server. • Works in server-to-client direction only • Used to send Message Notifications or Continuous Data Streams. • Support a lot of Browsers but Not supported in IE.
- 15.
- 16. WebSocket • A newHTML5 API that enables bi-directional, full duplex communication between the browser and server. • Fastest solution • Issues – Supported only on latest browsers – Works only with IIS-8.0
- 17. SignalR • SignalR isa library for ASP.NET developers. Used to develop Real Time Web Application. • Makes use of Push Technology. • Provides Abstraction over the set of transports. • Open Source available on Github!!!
- 18.
- 19. Transport Priority WebSockets Server-Sent events ForeverFrame (IE hack) Long Polling HTML 5 transports Comet transports
- 20.
- 21. Persistent Connection • low-levelcontrol to manage connection. • Contain events like “OnConnection”, “OnDisconnection”, “OnReconnection” • We can write our own logic in these events.
- 22.
- 23. Hubs • Provides aHigh-level API. • Client calling Server. • Server calling Clients. (All, Groups, One). • Broadcasting messages to all connected clients.
- 24.
- 25.
- 26. How do Iget SignalR?
- 27.
- 28.
- 29. Routing is VeryImportant
- 30.
- 31. Client Calling ServerFunction
- 32.