Hi,
I noticed in the recent 'config weirdness' thread that QP does caching
for config calls. Could anyone summarize the nature of this caching?
I've got a lot of configuration directives of various sorts stored in a
database and I'm looking at making a config plugin to handle loading
them. I'm hoping that qp's caching will help and not hinder this:
are config directives cached at all when they're retrieved on account of
a hook_config plugin, or does the hook_config plugin get called
immediately whenever qp->config() is called, bypassing the cache?
how long does the cached config last? the life of the transaction? the
life of the connection? longer?
Thanks!
-Jared
--
Inbound and outbound email scanned for spam and viruses by the
DoubleCheck Email Manager: http://www.doublecheckemail.com/
