timeout behavior needs to be more robust in handling errors

Currently, we send the user back up to the main page in the event of many timeouts. It should be possible to show that there is no response from the server in a less disruptive way. Ideally, this would show the component that has received the timeout.

If the user has repeated timeouts in XHR calls, then we may want to try to reload the app (or for extra credit, load the UI from another node).