title: Use of /signalr/ping call when using long polling
body: <p>I'm using long polling with SignalR. I've found that user session ends (ASP.NET Session_End is being called) right after singalr based webpage makes <em>/signar/ping</em> request (<a href="https://drive.google.com/file/d/0Bwq671F6jO6oYTJFek9mV0dnTDQ/edit?usp=sharing">as shown in this screenshot</a>). I went through <a href="http://www.asp.net/signalr/overview/signalr-20/hubs-api/handling-connection-lifetime-events">http://www.asp.net/signalr/overview/signalr-20/hubs-api/handling-connection-lifetime-events</a> but couldn't figure out clear answers following questions.</p>
  
  <ol>
  <li>How to keep ASP.net user session alive from a signalr client webpage?</li>
  <li>What is the actual purpose of /ping?</li>
  <li>Is the timing for this /ping call configurable?</li>
  </ol>