I'm wondering why timeout not works for you? It just does the same thing you describing.
Timeout on queue is a cool feature that we already use. But we have set a long timeout (says 1 minute) and some users don't want to wait so long.
So we try another way: after a shorter timeout (says 20 secs), we popup a confirm box saying:
"The transaction seems take too long (perrhaps there is network problem), would you like to abort it (click on 'Ok') or would you like to wait a little more (click on cancel)'
Furthermore, in case of timeout or aborted request, what is the best practise to synchronize the browser page with view in the server ? (at the moment, we are reloading the page) ?
Unfortunatelly we curently do not have such api. So seems the only way is to set the timeout to smaller value. Thanks for bringing this it would be good feature to include while planning api for 4.x.1 of 1 people found this helpful
Alternatively, you could be a good idea to add an option in richfaces to retry to send the "timeouted" request.
When the timeout fires, the confirm box shows up and it is asked to the user if he wants to relaunch the failed request.
By the way, have you ever heard of ajax request hanging ?
This drives our users crazy !!