Hi
Jerome maybe you have change the doc (I don't check the files).
I just give some tips to prevent pb with the ext
si-block should not be use if you have a lot of different key.
-> the cronjobs will take to much time to update all your block.
si-block should not be use to display comments/user informations
You will have to build another dedicate extension.
You should use si-block "only" for menu/header/footer
Don't use the ext to bypass cache-content issue.
like cache-block, it's not really a good idea to have a very small TTL.
Like cache-block, when you move a si-block in a tpl, the ext will create a new file.
Check the table create by the ext, and clean unuse information (remove all data)
It's stupid to say but never use the extension with dev mode enabled on prod server...
it will slow down the website perf.
Take care:
The cronjob flush the content cache to generate si file.
If you use ezkeywords attribute and you have a lot of keyword/content, ou should increase the value of the cachetreshold (site.ini)
if not ezpublish can remove all your content cache each time the cronjob try to generate si-file.
more info
http://issues.ez.no/IssueView.php?Id=13429&activeItem=8
where is version for ez 3.x
more info on varnish and ESI
http://varnish.projects.linpro.no/wiki/ESIfeatures
http://varnish.projects.linpro.no/ticket/352 (esi and gzip page don't work)
