title: Should signalr server-side methods be async when calling Clients?
body: <p>I'm following the "SignalR Tutorial" on : <a href="http://www.asp.net/signalr/overview/hubs-api/hubs-api-guide-server" rel="noreferrer">http://www.asp.net/signalr/overview/hubs-api/hubs-api-guide-server</a></p>
  
  <p>So let's assume this simple Chat Method : </p>
  
  <pre><code>public void Send(string name, string message)
  {
       // Call the addNewMessageToPage method to update clients.
       Clients.All.addNewMessageToPage(name, message);
  }
  </code></pre>
  
  <p>Suppose that I have a Chat room with 50 000 users. Would there be any benefit of changing the Send method to be async, like this : </p>
  
  <pre><code> public async Task Send(string name, string message)
   {
       // Call the addNewMessageToPage method to update clients.
       await Clients.All.addNewMessageToPage(name, message);
   }
  </code></pre>
  
  <ul>
  <li>Will IIS hold the current Request (of the user who published the
  chat) and wait until every clients are notified?</li>
  <li>Is the call to "Client" totally asynchronous under the hood and the request is
  released at this point?</li>
  </ul>
  
  <p>Thank you!</p>