Hi,

Currently we have two ways of implementation for proxy includes: ESI for Varnish and SSI for Nginx. The only difference between them is what directives are inserts in the HTML code. Why don't we just create a backend for both SSI and ESI (it would be the same backend as you have right now), and give another chance to the http://dgo.to/ssi project. SSI is pretty useful feature for sites that uses nginx, but currently we have no implementation for that in Drupal.

So my point is to run through a next steps:

  • Separate (S,E)SI API from your module and use it as an base API for both SSI and ESI.
  • Become a co-maintainer for SSI (this is task for me :-) )
  • Work together on SSI, ESI and (S,E)SI API to make this thing rock in Drupal.

Then I'm going to add implementation with Memcache Storage, so we may return blocks from cache without full bootstrap (just like a page cache for anonymous users). That would be great performance improvement for high-load projects.

Moreover, we can write implementations for blocks, panels, pages, nodes, users, taxonomy terms and other entities and content blocks.

Just let me know if you like this idea. Generally, if you have no time I can do everything myself, but I don't want to duplicate code on drupal.org, so I'm asking for you assistance here.

Kind wishes,
Spleshka.

CommentFileSizeAuthor
#1 Screen Shot 2013-10-14 at 14.50.40.png133.46 KBmanarth
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

manarth’s picture

Hi Spleshka,

The ESI module already has support for SSI tags (and SSI remote tags as well, for mod_publisher). There's a configuration page at admin/config/development/esi to control this setting. ESI 7.x-3.x has a pretty good system for abstracting this if we need to add support for similar tags.

A cache system for authenticated users is a great idea, and something I've been mulling over for a while now. It's something that a number of other tools and modules could use, so I thought rather than trying to plug it into ESI, if I were to start on that, I'd build it as a separate standalone module.

--
Marcus

Grayside’s picture

I've noticed that the Authcache module has launched into an ESI skunkworks project as a series of project sub-modules.

andypost’s picture

Issue summary: View changes

And now there's big_pipe and d8 port coming

dstuart’s picture

Status: Active » Closed (outdated)