On Thu, 2012-02-02 at 16:01 -0800, Nick Kew wrote: > On Thu, 02 Feb 2012 09:00:25 -0800 > Kevin Fox <kevin....@pnnl.gov> wrote: > > > Re-asking on the devel list instead. > > > > What is the current state of the trafficserver-plugins/esi plugin? > > Do you have an actual use for it? > > I ask because when I wrote an ESI parser module for HTTPD, it attracted > no real interest and I abandoned it. I have the impression that ESI > is just used by a handful of orgs, each with its own implementation. >
It looks potentially useful for a project I'm working on. I decided to evaluate various ESI processors and have thus far not found a good open source implementation. I'm thinking it may be a chicken and the egg problem. No one tries using ESI since there aren't good open source implementations providing it, and whatever documentation there is sucks. There are not good implementations of it because no one is using it. Catch 22. I think if someone can provide a stable ESI module for long enough and a document describing how to configure it, people would start showing up. Anyway, thus far I have looked at Squid, Varnish and Symfony's ESI implementations and found them all lacking in one form or another. Those are really the only implementations that show up in a Google search. Traffic Server doesn't really show up but I just happened to accidentally stumbled upon the trafficserver-plugin repo and see it. I had hoped that because Yahoo developed the ATS ESI module, it would be in better shape. But, after a bit of bug fixing, the ATS's ESI module looks to be working pretty well and looks more feature complete then some of the alternatives I've tried. Thanks, Kevin
