Monday, 4 February 2013

Requests for comment/Caching HTML Fragments (ESI)

Initial version


New page


== Background ==

Both Varnish and Squid provide a methodology to assemble pages on the front end cache layer. This technology is called 'Edge Side Includes' and was originally proposed by Akamai before it was accepted as a [https://www.w3.org/TR/esi-lang formal standard by the W3C]. It's mostly used for separating the site skin, also known as chrome, from the page content. It can also be used to substitute in content more appropriate to the device at hand, or according to cookie/get parameter values.



Because the original request page and the fragments (this can be recursive) can be cached separately, it allows for more effective cache management and more flexible site behavior -- think of skin hook changes, username includes, etc.



* [[w:Edge_Side_Includes|EnWiki page on ESI]]

* [https://www.varnish-cache.org/docs/3.0/tutorial/esi.html Varnish documentation]



=== Past History ===

Deployment of ESI via Squid is not possible due to performance limitations in Squid3 -- but the mobile team has been having great success with deploying it in Varnish via the mobile frontend.



== Use Cases / Requirements ==

=== CentralNotice ===

Stuff



=== MobileFrontEnd ===

[todo]



=== Parsoid ===

[todo]



== Suggested API ==

[todo]



== Performance Concerns ==

* Speed performance [todo]

* Memory performance [todo]

No comments:

Post a Comment