Bug 183213 - Message to user when the connection is lost
Summary: Message to user when the connection is lost
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: Future   Edit
Assignee: Rüdiger Herrmann CLA
QA Contact:
URL:
Whiteboard:
Keywords: consistency, info
: 183487 187276 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-04-19 11:50 EDT by Roberto Sanchez CLA
Modified: 2007-09-11 10:03 EDT (History)
3 users (show)

See Also:

Attachments
request-failure.diff (1.17 KB, patch)
2007-04-20 20:26 EDT, Benjamin Muskalla CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roberto Sanchez CLA 2007-04-19 11:50:41 EDT 
When connection with server is lost the application in browser seems blocked from user point of view, I think that would be desirable a message window (i.e: window.alert("...")) which tells user that the server is down or unreachable.

The message should be modified by developer.
Comment 1 Benjamin Muskalla CLA 2007-04-20 20:26:27 EDT 
Created attachment 64503 [details]
request-failure.diff

Attached is a little patch which listens to the requests status and alert the user if the request failed or has a timeout. As I see this as an important bug, we should maybe split it and file a new feature request for customizable error messages with a lower priority.
Comment 2 Benjamin Muskalla CLA 2007-04-20 23:40:17 EDT 
Maybe this could shutdown the application and redirect to an error page (see bug 183487)
Comment 3 Roberto Sanchez CLA 2007-04-22 06:16:03 EDT 
Hi Benjamin, I was testing the patch and it works fine when the server is shutdown or unreachable, Good! :-). However when the server is rebooted, I supossed that in this case there is a http session problem, the client looks like with server shutdown, that is, The client can't do anything but It doesn't appear any message on screen.
Comment 4 Rüdiger Herrmann CLA 2007-05-16 11:38:15 EDT 
There are three categories of errors that should be handled separately:
- 'fatal' server errors: usually send a complete HTML page that should be displayed as is
- session timeout: the user should be notified that a new session was initiated
- temporary (connection) problems: the user should be informed and retry if applicable.
Comment 5 Rüdiger Herrmann CLA 2007-05-16 11:40:12 EDT 
*** Bug 183487 has been marked as a duplicate of this bug. ***
Comment 6 Rüdiger Herrmann CLA 2007-05-16 12:57:53 EDT 
A further issue that must be solved is opening the same RAP site in different browser tabs (they share the same session).
Comment 7 Rüdiger Herrmann CLA 2007-05-16 12:58:30 EDT 
*** Bug 187276 has been marked as a duplicate of this bug. ***
Comment 8 Rüdiger Herrmann CLA 2007-09-05 14:43:41 EDT 
The original reason this bug was for is fixed in CVS HEAD.
If connection problems occur, the user is given a chance to resend the request or cancel the operation. In the latter case, an error page is written and the client-side application terminates.

I will leave this bug open until the other items are done.
Comment 9 Rüdiger Herrmann CLA 2007-09-11 10:03:55 EDT 
The remaining issues (see comment #6) are implemented and committed to CVS HEAD.