What?
If the user manually adds a server manually then you use the name or the
address that they enter. If the user 'favourites' a server that they
are playing on then you use the name if the server has one configured,
or the address if not.
If you want to include the case where a user 'favourites' a server that
they aren't playing on, then the client just needs to ask the server
whether it has a 'name' set, and use that.
There's NO NEED to change the master servers.
If users do a list and some of the names are no longer valid then treat
it exactly the same as if the server itself doesn't respond.
There's no need for some crazy back-end thread updating addresses, you
look it up when you need it. DNS servers have caching, there's no need
to reproduce that functionality in the client.
If the DNS servers aren't working then the user will be more worried
about not be able to access the web.
Summary:
1) A cvar for storing the server name.
2) Client can store a name rather than address in favourites.
3) A client can ask a server for its name.
Björn Rohlén wrote:
This might not be as easy as it sounds. SAF might look something like this:
- Did user add by hostname or ip4/ip6? store accordingly, no reverse lookup.
- If user added by hostname, resolve and store ip and hostname accordingly,
reverse lookups still useless.
- Solve the problem with not sending a whole barrel of queries from the
users favorite list when some crazy bastards have a hundred or so of them,
click the fav-tab and whine to no end when 15-30 of them no longer resolves
and the oddities that follows due to timeouts.
Now....
Possibly letting the user update the stored static ip if s/he chooses to, or
do it slowly in the background (awesome, more threaded bugs, leaks and
overcomplicating things). Confusion from "casual" players with the
updating-process commences. DNS-problems yet another point of failure when
people are trying to play online. Should masterservers be rewritten to allow
server operators to list their hostname on them to serve the clients?
Obviously this would be a very bad idea, so we´re back to favorites. ALL OF
THIS for manually adding hostnames to favorites?
Oh yeah, this will be fun.
-The Gryzowrg
On Fri, Jul 1, 2011 at 8:54 AM, Andrew Armitage <[email protected]>wrote:
This would make the lives of server admins a LOT easier.
Moving the server from one machine to another, for upgrades, extra capacity
etc. has always been a nightmare, and it takes ages to get our irregular
players back.Victoria Conlan wrote:
If they all remembered us by name then it would be a doddle!
A
On 25/06/2011 01:02, Guy Watkins wrote:
The hostname should be in a CVAR and returned when the server is queried.
It could be displayed in the browser without ever looking it up, but no
need
to display it in the browser, since you know the IP address at this time
and
can connect to it by IP. However, when you save it in favorites, it
should
save the hostname if one exists in the CVAR.
Maybe the browser could display the hostname when you hover over an entry?
This was talked about before on May 10 2010 relating to IPv6. The subject
was: "IPv6 Support"
Like this:
sv_hostname=myserver.com:27016
Guy
______________________________**_________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/**mailman/listinfo/hlds_linux<http://list.valvesoftware.com/mailman/listinfo/hlds_linux>
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
