15 Nov 2011 8:06 AM #1
Gracefully Handling External Request Timeout and Errors
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?
17 Nov 2011 9:54 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
Listening to the exception event on a Store should handle getting these timeouts or bad status codes. Then if you have history and need to go back, call the browser's history.back()Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services email@example.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.