ASP.NET SignalR – Clients

Outline

1. Hub Consumers

2. jQuery Clients

3. .NET Clients

 

1. Hub Consumers

 

2. jQuery Client

First approach:

jQuery with Proxy – part I

Demo 1 – UI preparation

1. Must include both javascript files, jQuery.js & SignalR.js BEFORE 2. SignalR/Hubs

2. Must include SignalR/Hubs

3. Include personal javascript file

 

Demo 2 – SignalR Utilities (signalr.exe) to generate server.js file

 

jQuery with Proxy – part II

 

jQuery with Proxy – part III

 

Demo 3 – Chat.js

Explain above 3 points:

1. chat.client.newMessage –> newMessage() is a client event method that can be called from server side. Define client behavior first

2. Once button click, trigger server side event by this line of code chat.server.sendMessage(xxx), so all clients will run client side event newMessage() which defined in previous step

3. Enforce to use longPolling as transport negociation protocal and start hub connection

 

 

Demo – Join Group

Demo – Monitor (test fail)

 

Second approach:

jQuery without Proxy File

Demo

 

3. .NET Client

Demo – Win Form

 

Summary

ASP.NET SignalR – Hubs

 

Hubs Concept

Convention: 慣例，常規，習俗，公約，協定。For example, Coding Convention.

 

Programming Model

Context: 文章脈絡，事件的來龍去脈

 

Demo

 

Hubs Protocol

 

 

1. .NET 4.0 doesn’t support WebSocket, so it will use SSE (Server Send Event) as second priority

2. .NET 4.5 support WebSocket, so it will directly use it as first priority

 

Step 1: Negotiate, try WebSockets

Step 2.1: Connect, with WebSockets, but fail

Step 2.2: Connect again, with SSE, success

 

If change <httpRuntime targetFramework=”4.5” /> in web.config, WebSocket will be used

 

Force using LongPolling as transport negociation

 

Pushing Data: Clients

 

Clients.Others

Clients.AllExcept(Context.ConnectionId)

above 2 are equal too.

 

Pushing Data: Groups

 

Demo – JoinRoom(), SendMessageToRoom()

 

Hub Lifecycle

 

Demo

New a class, MonitorHub.cs

GlobalHost.ConnectionManager.GetHubContext<T>();

 

Summary