Quote Originally Posted by Larirawiel View Post
It depends how the value of 15 minutes is stored. If it is a constant somewhere in the sourcecode then it should be easy "fixable" by increasing the value to a much higher value without many changes in the client. And i also doubt that it would break something. But this would not be a real fix but more a mitigation.

A real fix should remove the disconnects every 15 minutes completely and then there should be a reconnect mechanism with more than one try.



Here is the link:
https://docs.google.com/document/d/1..._OdCBfejk/edit

Cheers
Ah thank you. Very interesting and illuminating Wireshark analysis. The evidence seems pretty overwhelming, that our client software is at fault, not the login server at SE's end. Ergo this could easily be patched, presumably lessening the end-user frustrations from 2002 errors and losing our spots in the queue.

I'd like to see SE respond to this explanation, and offer us their own, hopefully transparent and easily understood, reason for the current login situation.