A load balancing and spread the timing for the servers so the load is spread evenly would then easy to make into it as well, and would benefit valve.... hell, they can even make it so that the server only goes updating once the "varnish cache server" has done its job. Server goes in "Guru Meditation" till the update is there. It will go updating once it turn is up "XID: 462613671478"
But no, they like the auto update feature.... everybody hammering their update servers at the same time, repeatedly cos the update didn't work well or give nice exit codes, clients dropping connection and w/e always happens with a 10+ byte update. >________________________________ > From: Eric Riemers <[email protected]> >To: 'Half-Life dedicated Linux server mailing list' ><[email protected]> >Sent: Wednesday, 18 January 2012, 11:14 >Subject: Re: [hlds_linux] Mandatory Team Fortress 2 Update Released > >All tf2 servers, issuing a quit at the same time.. I wonder what the >download server would think of that.. ;-) > >-----Original Message----- >From: [email protected] >[mailto:[email protected]] On Behalf Of dan >Sent: woensdag 18 januari 2012 10:43 >To: Half-Life dedicated Linux server mailing list >Subject: Re: [hlds_linux] Mandatory Team Fortress 2 Update Released > >On 18/01/2012 08:58, PharaohsPaw wrote: >> Looks like about all I can really do if I want a true "fuhgeddaboudit" >> auto-updating solution > >The only way we can get this is if Valve fix -autoupdate > >Whatever 3rd party tool someone else writes to autoupdate may require >updating itself if Valve change something, defeating the purpose of using >it. >"game changes....oops the tool breaks" Since debugging the tool is more >complicated than doing the thing the tool does, it's pointless. > >That's how Steam works, it updates itself and it updates the games. So, >modulo bugs, your games update without needing intervention or 3rd party >tools. > >That's the solution to this, Valve need to speak to the people who wrote >Steam about how they did it ;) > >Seriously though, surely all that autoupdate needs to do is, instead of >outputting the console messages over and over like it currently does, is to >issue a quit. >The restart will then update. That's what I do, after all, when the console >spams the messages, type 'quit' in console. What's the big deal I'm missing >with making it do that? I can't believe it would take more than 15 minutes >to do if you spent 10 minutes in the snack room trying to choose between the >giant pink cookie or the healthy salad bar. But, there must be some reason >they haven't done it. > >A gifted programmer might even make the disconnect message the clients get >say "Hey, we're updating, restart TF2 and come back later." but that's icing >on the cake. > >In the meantime, it's manual updates. > > > >-- >Dan > >_______________________________________________ >To unsubscribe, edit your list preferences, or view the list archives, >please visit: >https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > > >_______________________________________________ >To unsubscribe, edit your list preferences, or view the list archives, please >visit: >https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux > > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
