fre 2007-05-18 klockan 10:45 +0800 skrev howard chen: > thanks for reply first. i think the point of using ESI is to do some > user customization at the edge servers for performance gain. Yes... > such as the yahoo homepage, it contains your name at the top if you > have been logged in, isn't? Might. Many others do. > the drawback of this approach is contents can't be cached using squid, > which should suppose reduce the loading in the backend web server... > > i really want to know if other has good suggestion in the above > case...seems reverse proxy didn;t help in the case... ESI is a technology you mainly deploy on the reverse proxies. It's not generally something which will run on local LAN->Internet proxies as the content served between the web server and the ESI capable device is different than what is delivered to the end-user browser. With ESI that web page gets split into N components, each cached separately by the reverse proxy. For a medium site this serves as an flexible alternative to using memcached etc to cache database queries and other resource intensive operations, instead moving the query caching to HTTP reverse proxies. For a huge site it provides an easy means of scaling the above up effectively unlimited by deploying a cloud of ESI capable and caching reverse proxies. Deploying a large set of "dumb" proxies is easier than deploying a larger set of heavy web servers. Regards Henrik
Attachment:
signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel
