Better handling of when client becomes disconnect from database

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Work on a document on a remote client
2. Disconnect server db host machine from network
3. Make a new change on the current doc and then save doc
4. Observe bad error message

What is the expected output? What do you see instead?
Expect to see a message like "Could not connect to server"
but instead get error msg: Error saving transcript. REST service failed
because:"

What version of the product are you using? On what operating system?
0.9.3b1, linux

Please provide any additional information below.

Original issue reported on code.google.com by swami.ke...@gmail.com on 30 Mar 2009 at 5:23

[GoogleCodeExporter]

Expanding this issue to the general handling of when the database becomes 
unavailable
for whatever reason. If it does become available we want to be able to 
reconnect so
that we can save our changes. This is currently not possible.

Original comment by mjc1...@gmail.com on 31 Mar 2009 at 4:12

• Changed title: Better handling of when client becomes disconnect from database
• Changed state: Accepted
• Added labels: Priority-Medium, Difficulty-Low, Defect-Release0.9.3b1, Milestone-Release0.9.3
• Removed labels: Priority-Low

[GoogleCodeExporter]

Fixed in r264.

Not really tested, so please do so

Original comment by mjc1...@gmail.com on 31 Mar 2009 at 4:18

• Changed state: Fixed