Thanks for your reply. We are actually using ESIs in one place or another and one of the projects I have in mind for refactoring currently uses ESI to achieve something similar. Varnish however is an additional layer on the server that in many of our cases is not really necessary (as in either not easily available, not maintainable or simply not justified for the amount of traffic). But more than that I think it is not suitable as a default when developing something with reusability in mind. I feel that users of a package are still free to include the partials through ESI or SSI, if their stack provides that option. But if not then maybe (or maybe not) the outlined code would be an option.
-- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e4db32b1-b762-4140-ac1e-f3cad06ed251%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
