Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!nrl-cmf!ukma!gatech!dcatla!dnwcv
From: dnwcv@dcatla.UUCP (William C. VerSteeg)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  Multiple TCP/IP servers on one host
Message-ID: <9017@dcatla.UUCP>
Date: 12 Sep 88 13:25:09 GMT
References: <8809111732.AA08216@uc.msc.umn.edu>
Reply-To: dnwcv@sune.UUCP (William C. VerSteeg)
Organization: DCA Inc., Alpharetta, GA
Lines: 12
Summary:Think about client caches

Many ways have been discussed to make a mapping between one logical 
name and many IP addresses. These schemes all rely on having a machine 
resolve a name every time it wishes to open a circuit. Most implementations
have caches, do they not? It seems that for this to work, a resolver would 
need to tell a client "don't cache this response". Then the next time 
a circuit was established, the resolver would be able to look at the 
available resources and determine which IP address to return.
Don't get me wrong, I don't think we should really do this, but if one wanted
to have total control over resource allocation, caching techniques would 
have to be considered.

Bill VerSteeg