title: SignalR: how to survive accidental page refresh
body: <p>Imagine there is a chat web app between two browser clients using SignalR. What is the best approach to survive accidental F5 hit done by one of the client?</p>
  
  <p><a href="http://www.kevgriffin.com/maintaining-signalr-connectionids-across-page-instances/" rel="noreferrer">Here</a> is described the strategy using cookies together with custom SignalR IConnectionIdFactory. But the author of the article says <em>"The SignalR team doesn’t recommend this action"</em>. So what is the recommended architecture?</p>