hello, thanks for reply first. i think the point of using ESI is to do some user customization at the edge servers for performance gain.
such as the yahoo homepage, it contains your name at the top if you have been logged in, isn't? 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... On 5/17/07, Henrik Nordstrom <[EMAIL PROTECTED]> wrote:
tor 2007-05-17 klockan 00:41 +0800 skrev howard chen: > This is interesting...ESI seems to be around for a number of years, > claimed to be lead to great improvements... For semi-dynamic web sites with reverse proxies in front it's potentially a great boost. > but no one care abt it? Or other better alternatives? What are the difficulties? Requires a bit of change of state of mind to deploy. It's no longer the web servers responsibility alone to assemble the web page. Regards Henrik
