public
Description: ESI implementation for Rack
Homepage:
Clone URL: git://github.com/joshbuddy/esi-for-rack.git
name age message
file README.rdoc Tue Jul 21 05:48:16 -0700 2009 added a readme [joshbuddy]
file Rakefile Wed Nov 25 18:42:30 -0800 2009 fixed depedencies. added gemcutter tasks [joshbuddy]
file VERSION Wed Nov 25 18:42:44 -0800 2009 Version bump to 0.0.4 [joshbuddy]
file esi-for-rack.gemspec Wed Nov 25 18:42:52 -0800 2009 Regenerated gemspec for version 0.0.4 [joshbuddy]
directory lib/ Wed Nov 25 18:42:30 -0800 2009 fixed depedencies. added gemcutter tasks [joshbuddy]
directory spec/ Wed Nov 25 18:42:30 -0800 2009 fixed depedencies. added gemcutter tasks [joshbuddy]
README.rdoc

EsiForRack

What is ESI?

ESI is a standard way to assemble pages. This spec is supported by several reverse proxies.

slideshare.net/joshbuddy/to-the-edge-of-web-performance-and-beyond

Usage

In your builder, just use it.

  use EsiForRack

In your HTTP responses, just normal ESI tags. If you’re working within Rails, give Spackle a try.

github.com/joshbuddy/spackle

Here is an example of a response that would be parsed by EsiForRack

  <html>
    <body>
      <esi:include src="/helloworld"/>
    </body>
  </html>

In this case, a request to /helloworld would be made by EsiForRack to fill in the request. If your application sent: "Hey world" as a response to /helloworld the above example would be interpolated to:

  <html>
    <body>
      Hey world
    </body>
  </html>