Downloaded 10 times
![QueryString • Query string data. – In Server • Microsoft.AspNet.SignalR.Hosting.INameValueCollection queryString = Context.Request.QueryString; • string parameterValue = queryString["parametername"] – In Client • $.connection.hub.qs = { username' : ‘value' }; • You can add query string parameters in the client by configuring the connection, which is a convenient way to pass data about the client from the client to the server.](https://image.slidesharecdn.com/signalr2-150502135232-conversion-gate02/75/Signalr-with-ASP-Net-part2-11-2048.jpg)
Uploaded byEsraa Ammar
Signalr with ASP.Net part2
This document discusses various attributes and techniques used in SignalR hubs including the HubName and HubMethodName attributes, strongly typed hubs, synchronous vs asynchronous methods, passing complex objects and client information to hubs, and selectively targeting clients when sending messages from hubs using methods like Clients.All, Clients.Caller, Clients.Group, etc.
Signalr with ASP.Net part2
- 2. Topics Focused On!!! •HubName Attribute • HubMethodName Attribute • Strongly-Typed Hubs • Synchronous – Asynchronous Method • Complex object • Information about the client • Selecting which clients will receive the RPC
- 3. HubName Attribute If youwant to specify a different Hub name for clients to use, add the HubName attribute.
- 4. HubMethodName Attribute If youwant to specify a different Hub method name for clients to use, add the HubMethodName attribute.
- 5. Strongly-Typed Hubs To definean interface for your hub methods that your client can reference.
- 6. Synchronous – Asynchronous Method Makinga Hub method asynchronous avoids blocking the connection when it uses the WebSocket transport. When a Hub method executes synchronously and the transport is WebSocket, subsequent invocations of methods on the Hub from the same client are blocked until the Hub method completes.
- 7. Write async method •Server:
- 8.
- 9.
- 10. Information about theclient • The connection ID of the calling client. – string connectionID = Context.ConnectionId; The connection ID is a GUID that is assigned by SignalR (you can't specify the value in your own code). There is one connection ID for each connection, and the same connection ID is used by all Hubs if you have multiple Hubs in your application.
- 11. QueryString • Query stringdata. – In Server • Microsoft.AspNet.SignalR.Hosting.INameValueCollection queryString = Context.Request.QueryString; • string parameterValue = queryString["parametername"] – In Client • $.connection.hub.qs = { username' : ‘value' }; • You can add query string parameters in the client by configuring the connection, which is a convenient way to pass data about the client from the client to the server.
- 12.
- 13. Selecting which clientswill receive the RPC 1 • All connected clients. – Clients.All.ViewMessage(name, message); • Only the calling client. – Clients.Caller.ViewMessage (name, message); • All clients except the calling client. – Clients.Others.ViewMessage(name, message); • A specific client identified by connection ID. – Clients.Client(ConnectionId).ViewMessage(name, message);
- 14. Selecting which clientswill receive the RPC 2 • All connected clients except the specified clients, identified by connection ID. – Clients.AllExcept(connectionId1, connectionId2).ViewMessage(name, message); • All connected clients in a specified group. – Clients.Group(groupName).ViewMessage(name, message); • All connected clients in a specified group except the specified clients, identified by connection ID. – Clients.Group(groupName, connectionId1, connectionId2). ViewMessage(name, message);
- 15. Selecting which clientswill receive the RPC 3 • All connected clients in a specified group except the calling client. – Clients.OthersInGroup(groupName).ViewMessage(name, message); • All clients and groups in a list of connection IDs. – Clients.Clients(ConnectionIds).ViewMessage(name, message); • A list of groups. – Clients.Groups(GroupIds).ViewMessage(name, message);
- 16.
- 17.