Wednesday 29 June 2005 12:50:05 am

Thanks for the pointers. If you have a minute can you clarify one of your points - you say <i>you have to remove all dynamic content</i>. Do you mean within a specific tpl file or within a "delivered" page (i.e. the final full page sent by the web server)?

* If the answer is removing dynamic content from specific tpl files (e.g. pagelayout.tpl), can you <i>include</i> external templates that encapsulate any dynamic content you wish to deliver as part of the page (I guess via shtml in the resultant static cache)?
* If the answer is removing <b>all</b> dynamic content from the served page and you have limited dynamic user/date specific content e.g. displaying user name, do you use cookies to pass the info to javascript in the page that can manipulate your "dynamic" content?

thanks

Geraint

Friday 13 January 2006 10:37:36 am

Hi Georg,

we just released a patch allowing to use PathPrefix with static cache. I think you find this intersting as you already posted a bug about this issue: http://ez.no/bugs/view/6780

You can find the patch for 3.6.4 at pubsvn:
http://pubsvn.ez.no/community/trunk/hacks/staticcache_with_path_prefix/

Greetings, Daniel.

Daniel Beyer
_________________________________
YMC AG
Kreuzlingen, Switzerland
web: www.ymc.ch
____________________________________

Sunday 06 April 2008 4:04:04 pm

"quite old topic... not much interest anymore... I removed the sticky..."

On the contrary, I would suggest there is a lot interest in what you call "Static Cache" (other descriptions are "Static content export", "Static Deployment" etc). Plone has had this functionality, allbeit as a free plug-in, for years.

The up-and-coming (very cool) Silverstripe CMS (www.silverstripe.com) already has this basic built-in and the developers are actively working on improving it for "Enterprise" class interface and functionality.

"I think people should start using reverse proxies over static cache."

For some organisations such as ours, the overhead in managing, configuring and maintaining a reverse-proxy was such that it was no-hassle at all in comparison to simply employ a system that generated flat HTML from dynamic content.

We have no use for public logins, calendar or forum functionality, just data that is occasionally requested in massive numbers - in very, very short timespan.

I am actively looking at ezPublish for a replacement for our current CMS, and its ability to create a static "cached" representation of files and file hierarchy is an absolute key component to our using it or not.

Thanks to the other posters to this thread, very useful information. :-)

Russell Michell, Wellington, New Zealand.
We're building! http://www.theruss.com/blog/
I'm on Twitter: http://twitter.com/therussdotcom

Believe nothing, consider everything.