Sounds a lot like the DNS server hierarchy, but for a slightly different
purpose (OK, maybe a bit more than slightly :-).
Local servers would be 100% necassary since without them faults with the
root PAC server could cause major problems, and in places far from the
root PAC server there could be severe lag when initially loading the
script. A local server would only need to cache the PAC script (maybe
several) and nothing else, so it could be a very stripped-down web server.
The root PAC server would need more functionality, and a lot more
processing resources.
Thinking about it, it would probably be useful to let the local PAC server
have the ability to figure out who needs which PAC, since many ISPs are
large enough to have multiple caches on different subnets.
-Bill
On Mon, 8 Sep 1997, Dave Zarzycki wrote:
> The Proxy Auto Configuration (PAC) script could be generated by a Perl
> script on the server side tailored specifically for the client. Or the
> "global PAC server" could be a proxy for PAC servers around the world, so
> that clients don't have to keep track themselves of what server to query.
> Or change their client if the local PAC server goes down.
Received on Tue Sep 09 1997 - 08:31:51 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:36:57 MST