At 14:28 25/01/2003, you wrote:
1 round trip is long enough... say you're querying 30'000 game servers. it's now going to take twice the time to get a reply from them, might as well go make 6 cups of tea (instead of the normal 3) before the query process finishes :)The only thing that would slow down is the time it takes for the query to produce results. And, unless the server ping is very high, that isn't even going to be THAT much. And you don't want to play on a server with 500+ ping anyways, so who cares about the query speed of those. Also, an effective handshake would be able to reuse the same ID for the same connection a few times. So the only added lag is 1 round trip to the gameserver.
Heh, have you seen gamespy lately :)As for waste of resources.... GameSpy, which is a quite 'heavy' program, used to run fine on my P233 with 32 MB RAM... Surely, the current 500 Mhz+ machines with 128MB RAM+ can handle a few more bytes per server... I mean, it's not that the server name, IP, port, playercount, ping, player data, rules, etc.. take up 0 bytes of memory.
Anyway, the point still stands that this should be fixed on the various network levels, not the application layer.
Kris.
_______________________________________________
hlds_apps mailing list
[EMAIL PROTECTED]
http://list.valvesoftware.com/mailman/listinfo/hlds_apps
