Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Your best bet is likely to host the SignalR server along with your MVC app on IIS. Don't worry about self hosting since you already have IIS set up.</p> <p>I think you will have an easier time using Hubs over PersistentConnections since Hubs allow for RPC.</p> <ul> <li><a href="https://github.com/SignalR/SignalR/wiki/QuickStart-Hubs" rel="nofollow">https://github.com/SignalR/SignalR/wiki/QuickStart-Hubs</a></li> <li><a href="https://github.com/SignalR/SignalR/wiki/Hubs" rel="nofollow">https://github.com/SignalR/SignalR/wiki/Hubs</a></li> </ul> <p>In your console apps and windows services, I would suggest using the SignalR .NET client.</p> <p><a href="https://github.com/SignalR/SignalR/wiki/SignalR-Client-Hubs" rel="nofollow">https://github.com/SignalR/SignalR/wiki/SignalR-Client-Hubs</a></p> <p>You can push and pull data from the console apps to the SignalR server which can then in turn can act as a <em>proxy</em> to the browser clients. Of course, the SignalR server can proxy in both directions allowing any client(s) to send realtime messages or requests to any other client(s).</p> <p><a href="https://github.com/SignalR/SignalR/wiki/SignalR-JS-Client-Hubs" rel="nofollow">https://github.com/SignalR/SignalR/wiki/SignalR-JS-Client-Hubs</a></p> <p>Your .NET and JS clients can access the same Hub or different Hubs. If all the clients access the same Hub, you might want to separate them into groups so you can distinguish between the two types of clients. If you choose to use multiple Hubs, you will likely want to make use of <code>GlobalHost.ConnectionManager.GetHubContext&lt;MyHub&gt;()</code> to communicate with clients connected to a different Hub than the one being called.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload