Complete.Org: Mailing Lists: Archives: freeciv-dev: September 2002:
[Freeciv-Dev] Re: new connect dialog (ver 2) (PR#1911)
Home

[Freeciv-Dev] Re: new connect dialog (ver 2) (PR#1911)

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: "Per I. Mathisen" <per@xxxxxxxxxxx>
Cc: Freeciv Developers <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: new connect dialog (ver 2) (PR#1911)
From: Mike Kaufman <kaufman@xxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 2 Sep 2002 16:17:10 -0500

> > Maybe you should. Just do
> >
> > #define AUTOCONNECT_INTERVAL        10
> > #define MAX_AUTOCONNECT_ATTEMPTS      10000
> >
> > and you're in.

I didn't understand what Christian wanted here in the first place.

> 
> How about restricting ALLOW_HACK to connections from localhost?

somebody tell me how to do this. Or provide some code. I'm uncertain how.
Are we guaranteed to have "localhost" as a connecting address? 

> 
> > > didn't kill off server on disconnect (want other people's opinion on
> > > this)
> >
> > Well, this can be discussed. I would say, kill the server. Just warn the
> > user that this stopsthe game also for the remote players. Can you detect
> > this (remote players) in an easy way?
> 
> Don't kill the server. That would be seriously annoying.

I tend to agree.

> 
> (Eventually we should consider migrating the server to one of the
> remaining players, though. Not a big deal, just PACKET_MIGRATE_SERVER to
> random other player who must spawn a server, then send all the data, then
> PACKET_CHANGE_SERVER to all players. This can also be a feature to reduce
> lag - migrate the server to the player with fastest connection. Anyway,
> blue sky item.)

yeah, no kidding.

-mike


[Prev in Thread] Current Thread [Next in Thread]