Page 2 of 2

Re: Round-Robin Balancing Implementation Question

Posted: Wed Jan 15, 2014 11:24 pm
by khal
biolizard89 wrote:With typical DNS, I'm under the impression that a name that uses round-robin load balancing will randomly pick one IP when it is resolved by a DNS client. This will last several hours due to caching. However, with Namecoin, the DNS server is often on localhost, and there is often no need for caching the result of the random selection. The simplest way to implement the random selection in Convergence for Namecoin is simply to do the random selection when each TCP request is made (instead of picking result[0], we pick result[rand()]).
Every website using sessions may be broken => do you want to login 4 for times, each time you click on a link, for each new ip ?
Some forms can use tokens stored in session to be sure the user has really displayed the form before submitting it (to avoid unsolicited submissions).

Big website may use or may not use centralized session systems (with instant or delayed synchronization).
So, a cache on the resolver should be be required.

Re: Round-Robin Balancing Implementation Question

Posted: Wed Jan 15, 2014 11:41 pm
by indolering
Tor provides its own DNS resolver, wouldn't it be easier/safer to just supply information to that DNS resolver?