Comment 3 for bug 1415925

It seems that this requires a blueprint as it's a far-reaching problem. Also, as we shift to an async client-side interface that processes timeouts on its own, this shifts the issue somewhat from the API layer to async behaviors on the client side. I suggest calling this Low for now, and having someone write a blueprint if they think it's important.