[geeklog-devel] geeklog-devel Digest, Vol 85, Issue 10

Michael Brusletten ironmax at spacequad.com
Wed Oct 16 17:56:33 EDT 2013


That sounds good to me.  Everything should be covered under this plan.  Any 
new plugins (or legacy plugins slated for upgrades) can take advantage of 
this new feature by having individual plugin config options.  The older 
plugins that have not been upgraded, should be able to work fine as your 
working with them now, because they would fall under one of the three areas, 
articles, staticpages, and blocks.  Are there variable hooks that allow for 
this, where the plugin can use when the author of the plugin decides to 


-----Original Message----- 
Message: 2
Date: Tue, 15 Oct 2013 19:23:16 -0400
From: "Tom" <websitemaster at cogeco.net>
Subject: Re: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 9
To: "'Geeklog Development'" <geeklog-devel at lists.geeklog.net>
Message-ID: <004601cec9fd$86f4c4a0$94de4de0$@cogeco.net>
Content-Type: text/plain; charset="us-ascii"

All object cache values can be set individually. I was just wondering  if we
wanted  customizable default value for any new objects. We current plan is
to add it in.


-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Michael
Sent: October-15-13 5:52 PM
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 9

I wonder if making the cache options available per article, staticpage, and
block with a default configured in the main configuration.  This way the
admin can decide on whats constantly changing or not.   I would suspect that

the stories would not change much, but then again, there could be items in
the stories that might change from outside sources, like maybe images or



Message: 1
Date: Mon, 14 Oct 2013 21:44:05 -0400
From: "Tom" <websitemaster at cogeco.net>
Subject: [geeklog-devel] Geeklog Caching
To: "'Geeklog Development'" <geeklog-devel at lists.geeklog.net>
Message-ID: <001601cec948$0824c9a0$186e5ce0$@cogeco.net>
Content-Type: text/plain; charset="us-ascii"

Okay I have the article caching pretty much done.

It works the same way as for staticpage and blocks where you can set an
individual story to cache from 0 to X seconds before it is recreated (0 is
off which is the default setting).

I have 2 questions which applies to all 3 objects being cached (article,
staticpages, blocks).

1) Do we want an always on cache option where the cache file is never
recreated unless the object is updated by the user. I can see it working
where the user enters a -1 (instead of a 0 to X) so the cache file is always

2) Right now all cache times default to 0 (off). Do we want 3 config options
to allow the user to set some other default?

With tests on my windows system I found very little gain in caching
articles, staticpages, blocks that have little more than text in them
(hundreds of a second difference). Where you really see a savings is when
these objects have to do some processing like with embedded autotags, php,
etc. At this point how long you want to cache the object for before it is
recreated depends on what the data is and if it ever changes and how often.



More information about the geeklog-devel mailing list