Handling dropped TCP connections more gracefully

[Timothy Arceri <t_arceri yahoo com au>]

Hi guys,


I'm looking into a solution for https://bugzilla.gnome.org/show_bug.cgi?id=615146 in particular I want to 
make Nautilus handle this situation more gracefully. As described in 
https://bugzilla.gnome.org/show_bug.cgi?id=515217 it is fairly common for firewalls and routers to break the 
TCP protocol an just drop connections without notifying anyone.

Currently if this happens and you try to do something in Nautilus you get a message like this:
“Opps something went wrong.
Unhandled error message: Internal error: The underlying SSH process died”  


After which the connection disappears and you need to remount it again (loosing you current location).

Now what I'm after is some advice on what you guys think needs to be done to improve the situation. 

To me it lookslike the solution is probably a combination of gvfs 
passing back a useful error code to Nautilus/filechooser/etc and then 
for Nautilus etc to catch the error and popup a dialog that allows you 
to either cancel or retry connecting.  The problem is currently gvfs just passes back a generic 
G_IO_ERROR_FAILED error code. 


Am I on the right track? Do you think that all that needs to be done from the gvfs side is to pass a better 
error code? If so what would you suggest? There isn't really anything that matches on 
https://developer.gnome.org/gio/2.32/gio-GIOError.html or is there more to this? I suspect there might be.

Tim