Show description

Listing 3-15. Message); } } } We get an instance of the Person object as a parameter and then call the client-side displayText method by passing the Name and Message properties as its parameters. On the client side, we have to make some modifications to pass an instance of this custom Person type with the additional data needed and then customize the client-side displayText method to accept an additional parameter and display it (see Listing 3-16). Listing 3-16. val() }); }); }); });

Here we customize the displayText method to receive two parameters from the server and display them appropriately.

HubConfiguration object. On the client side, we can change the location of the JavaScript reference to the dynamic hubs proxy to use this new URL (see Listing 3-6). Listing 3-6. NET SignalR assumes that your clients are connecting to your server component on the same domain as the execution location. NET SignalR domain. In reality, it might not be the case for bigger-scale applications. NET SignalR server independently from your main application on a separate domain and probably on separate servers.

The previous example of a personal blog can be used to describe why SignalR should not be used with content that is infrequently updated. In this scenario, a persistent connection is made every time a user visits the site. Because 34 Chapter 2 ■ Overview of SignalR the odds are that the content is not being updated while a visitor is visiting the site, no content is delivered using the persistent connection that was created. As with many personal blogs, there are very few interactions that a visitor is allowed to do, and the impact of the action does not need to be in real time.