15 Nov 2011, 8:06 AM
It seems like a common problem I am running into is that quit frequently requests timeout due to a less than ideal network connection. Other than increasing the timeout for a request I was wondering if anyone else had recommendations or implementations of gracefully handling this issue. From my own experience it seems like it would be ideal to carry out an action which takes the person back to the previous item when a card switch occurs. Than prompt them with a message to try again. However, I would like to establish a global way of achieving this, rather than replicating similar code every where. It seems like long term though that this may me something to consider when developing the routing or history implementation?