A prototype for Web Server Redirection. 
When a client issues a request for a file, request first goes to the server 
(obviously called Redirector). Redirector looks up its database and finds 
that the particular file request can be satisfied by Server A, and hence 
forwards the request for file F to Server A. Server A then sends the required 
file to the client. The servers storing files have capabilities to add/delete 
file provided that they send the information to the Redirector. The constraint
of problem was, Servers satisfying the requests were supposed to be non 
intelligent, hence use of servlets was strict no.