Talk:Edge Side Includes

Computing: Software / Websites Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Low-importance).
	This article is supported by WikiProject Websites (assessed as Low-importance).

"Bingo!"[edit]

What is edge level dynamic web content assembly? --Abdull (talk) 17:57, 19 December 2007 (UTC)[reply]

Applications ?[edit]

I guess if there were examples of what it is used for, then we would find it easier to understand. Are we talking about inserting adverts and news tickers into web-pages ? Where is the edge of the internet ? Would that be my ISP inserting adverts into pages I view ? Or my corner shop ?

--87.194.174.252 (talk) 16:39, 6 March 2009 (UTC)[reply]

A few use cases[edit]

In my experience, this is used on a web farm, rather than by an ISP. It's best explained by an example. Suppose you're BBC News. You're going to have hundreds of servers which serve requests. However, they tend to be hidden behind a load balancer. All requests for web pages on news.bbc.co.uk will go to that load balancer, which in turn determines which of the hundreds of servers to send your request. This all works fine, but given that news pages don't change very frequently once they're written, it'd be desirable to cache the news page on the load balancer. This will reduce the number of pages that need to be generated by the hundreds of servers. Again, this is all fine until you want to put changing content on the article page. For example, you want to include a bit of content that says "Most popular on the site today". This changes all the time; far more frequently than the article changes. So, this is where you use an edge-side-include.

When a visitor requests an article, the load balancing proxy server will look to see if it's got it in its cache. Most of the time it will. It'll then read it, determine there's an ESI tag in it - if there is, it sees if that page is in its cache. It then glues them together and serves them to the visitor.

I hope this makes sense. —Preceding unsigned comment added by Anonybob (talk • contribs) 17:01, 13 March 2009 (UTC)[reply]

Why links to companies in See Also section?[edit]

Why are there links to companies in the See Also section when there are already links in the body to each of the companies that support the spec? Seems like advertising. If they had content on their sites that discussed the issue that might be a different story. -- Dougher (talk) 01:50, 12 June 2009 (UTC)[reply]

fixed Justinc (talk) 11:08, 7 April 2011 (UTC)[reply]

Criteria for speedy deletion[edit]

CSD A7 requires that the article not assert the subjects notability. This article clearly asserts notability. The issue of whether that notability is sufficient is for an AfD. -Selket ^Talk 22:29, 7 September 2010 (UTC)[reply]

You can nominate it, if you see fit. I'm pretty apathetic at the moment. LiteralKa (talk) 22:33, 7 September 2010 (UTC)[reply]