[wp-hackers] overriding the built-in cache
skippy at skippy.net
Thu Jan 5 11:45:23 GMT 2006
David House wrote:
> On 05/01/06, Scott Merrill <skippy at skippy.net> wrote:
>>I am having some trouble with my wp-cron plugin, and I'm pretty sure
>>it's the new caching mechanism that's causing it.
> I thought one of the options this discussion in #wordpress produced
> was to use a direct query via $wpdb: did this not work?
I haven't gone the direct query route yet, because of Ryan's comments in
the category cache discussion:
> In WP, everything is public so plugin
> authors treat everything as fair game. Everything is not fair game. We
> need to do a better job of defining and documenting the boundaries, and
> plugin authors need to request API when there is something they need to
> get at. If plugins are accessing global variables and doing lots of
> SELECTs, they need to make use of existing API instead or request API
> where there is none.
skippy at skippy.net | http://skippy.net/
gpg --keyserver pgp.mit.edu --recv-keys 9CFA4B35
506C F8BB 17AE 8A05 0B49 3544 476A 7DEC 9CFA 4B35
More information about the wp-hackers