This is a good point and something which I think should be bourne in mind
when designing any client-server system. Due to the rapid growth of cheap
processing power we can often assume that the client machine will have
plentiful processing power but that the servers are likely to easily
become overloaded. This is especially true if the server is handling a
popular service and is getting a very large number of transactions from
widely dispersed clients, each of which has slightly different
requirements (due to different local images caches, hardware platforms, etc).
> Best of all I'd rather have the document author wait
> while their document is checked for errors and optimized for rapid retrieval
> just once so all 10,000 of us could enjoy the benefits.
Hopefully this sort of thing will become commonplace with the increased
use of validated HTML generators and browsers that flag HTML errors (after
all many of us use our browsers to check documents already - something
like Arena's ``Bad HTML'' is an excellent idea that all browser authors
should consider adopting IMHO).
Jon
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Jon Knight, Research Student in High Performance Networking and Distributed
Systems in the Department of _Computer_Studies_ at Loughborough University.
* It's not how big your share is, its how much you share that's important *