SignalR provides ConnectionId for each connection. To find which connection belongs to whom (the user), we need to create a mapping between the connection and the user. This depends on how you identify a user in your application.
In SignalR 2.0, this is done by using the inbuilt IPrincipal.Identity.Name, which is the logged in user identifier as set during the ASP.NET authentication.
The SignalR codebase includes a load-testing tool called Crank. However Crank can only test PersistenConnections but since you’re looking to test the SignalR Hub itself, you can use the sample tool provided by qburst.
The source code for this tool can be downloaded from here and this article should help you further.
As you may be aware you cannot directly load data files from another domain. This is a security issue that has been around for a long time and is commonly solved by sharing data through an API, REST or such.However there are ways around this and in this post we will be looking into JSONP.
In cases where cross-domain scripting is desired, CORS allows web developers to work around the same-origin policy. CORS adds HTTP headers which instruct web browsers on how to use and manage cross-domain content. The browser then allows or denies access to the content based on its security configuration.