Etria Lists

Reinout van Rees wrote:
> Tim Hicks wrote:
>> Mikel Larreategi wrote:
> 
>>> Do you mean that they should be in skins/Quills instead of browser?
>> No.  They are in there because they are wired up as Five views, rather
>> than skin-based templates.  This makes life better in some senses, but
>> also means that you can't customise them TTW.
> 
> It is not customising TTW that worries me so much, but caching.
> 
> Explicitly: atom.xml is uncachable by cachefu. Ouch, that's one of the
> biggest hits my website takes. Apparently it *is* possible to cache many
> Five views (with some *manual* effort, naming them one by one in
> cachefu), but for instance Rocky Burt couldn't get the atom template to
> cache because of some acquisition problem.

Ah, I'd heard mumblings about this on IRC, but didn't realise it was an 
insurmountable problem :(.

> So... To me, there really have to be really good reasons not to turn
> them into skin templates. "Speed" is often quoted as a reason, but that
> might actually sometimes work against it.

I didn't write things this way with speed in mind, but rather, to make 
reuse of the templates far easier across projects.  I'm pretty happy 
with the results as I have now written two products based on this that 
provide syndication feeds to many more object types 
(PloneboardSyndication and a branch of ATCTSyndication).

It also seemed like the right pattern to follow as it is the new-fangled 
Five/Zope3 way of doing things.  As that is the case, I presume people 
are thinking/working on ways to resolve these caching issues.  Or maybe 
that's just wishful thinking...


Tim