[geeklog-devel] 1.5 error.log when DB dies

[Tony Bibbs]

Joe,

You don't need anything unique in siteconfig.  Once GL decided to use the DB for settings it should honor that.

That said you can safely use the site_url from the DB to generate the key.  If Dirk so chooses to use the siteconfig.php that's fine too which was of my suggestions.  My point in all this was to make it clear to you you can use file-based caching if you wanted and that using memcached (or apc) would be unwise.

You've proven nothing I haven't already known about you...

--Tony



----- Original Message ----
From: Joe Mucchiello <joe at ThrowingDice.com>
To: Geeklog Development <geeklog-devel at lists.geeklog.net>
Sent: Wednesday, August 13, 2008 12:51:33 PM
Subject: Re: [geeklog-devel] 1.5 error.log when DB dies

At 01:31 PM 8/13/2008, Tony Bibbs wrote:
><snip>
>
>What am I missing now?
></snip>
>
>Most caching scenarios go like so:

<snip>Hello?!?? Author of the Caching Template Library here. The CTL 
can cache instances of filled in templates. Perhaps I know a lot 
about how caching works. 
http://www.glfusion.org/forum/viewtopic.php?showtopic=8024 But that's 
just a tangent....

>So if you have 10 geeklog sites the answer is to make sure $someKey 
>is unique.  This would be pretty easy, just pick something unique 
>from the configuration file (site_url, path, etc) and use it as the key.
>
>$someKey = md5($_CONF['site_url'] . '_' . $_CONF['path_logs']);

Have you forgotten the whole point of this exercise?

If you had $_CONF['path_logs'] available YOU WOULD NOT NEED TO 
RETRIEVE IT FROM CACHE. Likewise, if the database is down 
$_CONF['site_url'] is unavailable.

Now here is the important part: There is ///nothing/// unique in 
siteconfig.php.

Tony wrote:
>1) Cache the location of the ////log directory//// using PEAR's 
>Cache_Lite or Zend_Cache.  By caching the location to the ////log 
>dir//// to a file you get out of this, yet, still allow use of 
>DB-settings. [emphasis added]

My response was to put path_logs into siteconfig.php. Put something 
unique into siteconfig just so you can retrieve something else from 
cache is not nearly as simple as just putting $_CONF['path_logs'] 
into siteconfig and not shipping a whole cache library just so 
error.log can find its place.

I believe I've proven I am NOT missing anything. Where do I send the 
medical bill for the head trauma caused by my head repeated slamming 
into a brick wall?

----
Joe Mucchiello
Throwing Dice Games
http://www.throwingdice.com 

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://eight.pairlist.net/mailman/listinfo/geeklog-devel