title: How can Meteor handle stale connections?
body: <p>I am trying to somehow handle a scenario in which I am getting a corrupted application state:</p>
  
  <ol>
  <li>I first open the same app in two browser windows.</li>
  <li>Turn off wi-fi (or 3g) - connection becomes stale because it was not closed from the remote server.</li>
  <li>Perform a write operation in the first tab (the second tab will of course not update reactively).</li>
  <li>Turn on wi-fi.</li>
  <li>Perform a second write in the first tab (the second tab will now update reactively)</li>
  <li>So the first tab is now in a corrupted state. The first write will never sync to the server, and if the page reloads, that change will be permanently lost.</li>
  </ol>
  
  <p>Is there a way of handling this stale connection states? Meteor.status().connected remains true throughout this scenario. Is this a Meteor issue that needs to be resolved?</p>