Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Could these efforts not be amalgamated? Really appreciate the module, by the way, just hoping to minimize confusion and unnecessarily difficult upgrade paths :)
At the very least, perhaps you could explain in the project description how the approaches are different and why separate modules are needed? Thanks! You're awesome.
Comments
Comment #1
pounardSame features, it's indeed a duplicate, but not the same way of doing things.
I actually went to see the ESI module code before writing my own, I saw that it was rather old, no D7 version was showing up at this time, and I did mine for fun.
ESI API actually has an extra feature which is AJAX downgrade. I presume that it also have a better cache handling mecanism a better core features usage (the ESI D6 version does not do anything more than showing up blocks as ESI tags while ESI API provide an API with smart cache handling that can be used for anything).
That said, ESI module maintainers contacted me to ask to join efforts but then never answer back after myself when I said I didn't want to provide efforts for their module if I couldn't see their D7 code. Nevertheless, it seems (judging by what they said when contacted me) that they made a huge effort for third party integration with ESI, and it should be a good module, but I cannot judge since I cannot see it anywhere.
Comment #2
rfayWould appreciate if a compare and contrast with the ESI module on the project page.
Comment #3
pounard@#2 Job done. I can only assume stuff, so I did, my description is unlikely to be accurate.
Postponing the support request since ESI D7 doesn't seems to exist yet, please re-open if you have any further questions.
Comment #4
pounardIf nobody has nothing to add, I close the issue.