> > I tend to think that a CMS should *NOT* serve content straight from the > content repository, exactly for the reasons above: it's hard to > optimize it for that! >
I agree entirely! > The best (IMHO) architectural solutions for this is to have something > like > > frontend <--- repository <--- backend > > where "frontend" does the presentation stage and can do inverted > caching. This is the approach I am using (and I want to put slide into the space labelled repository). In fact, this ties in with your point about "bad marketing", I'd like to use slide as a content "repository" rather than a content "distribution mechanism". This is why I am raising objections to optimising for read-speed at the expense of code simplicity and performance of other "repository" activities. Cheers Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
