From: gah@ugcs.caltech.edu   
      
   Hans Rosinee  wrote:   
   > I'm in the need to test a client-server setup in the case of a very slow   
   > server response. A large number of thin clients chatting to a heavy loaded   
   > server via the HTTP protocol. The server could be located in another country.   
      
   > My idea is to setup a false DNS-server on the local network (where all the   
   > clients are) and thus make the clients talk to the server (on another   
   network)   
      
   I am not sure what is so false about it.  You can point your DNS records   
   to any host you want.   
      
   > via a some sort of HTTP echo-service or "Man In The Middle"-service   
   > somewhere out there. It is to much work to reconfigure all the   
   > clients to talk to this echo-service. Hence the false DNS-server   
   > (ettercap?). The "echo-service" of MITM should be configurable   
   > on delay, bandwidth-limiting, no response etc.   
      
   There are caching web servers.  Presumably you could set one   
   up somewhere with the cache TTL set very low, such that it wouldn't   
   do much caching.   You should be able to find someone that will   
   lease time on a host that you can use, and run whatever server   
   software you want.   
      
   Otherwise, I believe that some OS have controls on the throughput   
   of IP, I don't know that they have the ability to introduce a   
   constant delay.  Still, that may be enough.   
      
   -- glen   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)