[Computer-go] CGOS Dropped Connections - Two automatic losses on time.

Christoph Birk birk at obs.carnegiescience.edu
Mon Nov 8 16:40:14 PST 2010

On Nov 8, 2010, at 2:28 PM, Robert Finking wrote:
> On 08/11/2010 14:17, Don Dailey wrote:
>> One possible solution is for the server to force the previous login  
>> to disconnect if it thinks that player is currently connected.   It  
>> will send a quit command to the client and then realize there is no  
>> connection and this is trapped.
> It's a nice approach - simple and effective - but needs safeguards I  
> think. If two people are using the standard engine pack, the second  
> person who comes along will boot the first off the server. If the  
> first then tries to reconnect, they will boot the second etc.. How  
> about a 1-minute safeguard? An incoming login only boots the current  
> login if it hasn't been heard from for over 1 minute? On 13x13 and  
> 19x19 longer timeouts may be needed.

How about not booting the existing player at all, but refusing the  
of the 2nd one (as it is currently done). This allows a cron-job to  
the programm periodically.


More information about the Computer-go mailing list