2013-04-10 10:47 AEST by Arthur Barrett - On windows, clients can appear to intermittently hang for many many many reasons, eg:
* network failure
* failure to authenticate 'properly'
* failure of :ext: helper
* software failure (client)
* software failure (server)

If the client could have a thread running which accepts diagnostic messages from the 'main' thread and 
'logs' them/stores them - this could be 'queried' by some other diagnostic tool (see bug 5578).  

This 'client diag thread' could either always run, or be switched on by using the client diagnostics gui (see 
bug 5578).

Things that the diagnostic thread could have that could be passed to the diag GUI include:
* server version/client version
* protocol / CVSROOT
* is connection successful
* is auth successful
* had encryption or compression been negotiated
* how many bytes received/transmitted
* client trace or just last '100 lines' of trace
* last data read/last data sent