Hi,
Ben Coburn wrote:
On Apr 3, 2006, at 4:35 PM, Mario Emmenlauer wrote:
weired, as I have caching enabled, but still the utf8_substr-function
gets called every time the feed is requested. Did I just mis-hack
something (very likely) or does the caching work in a way that it
still
calls utf8_substr (in which case the caching obviously won't help)?
The cache is based on the following properties:
$_REQUEST['num']
$_REQUEST['type']
$_REQUEST['mode']
$_REQUEST['minor']
$_REQUEST['ns']
$_REQUEST['linkto']
$_SERVER['REMOTE_USER']
I think this may result in per-user caching to preserve the access
control from the ACL.
Are you using the current darcs version?
Nope, the last release version.
Untill recently the cache would
only last 5 minutes if there were new changes. If you have the recent
darcs version you can set rss_update in the configuration to a much
larger value (to get RSS update every 3 hours for example). AFAIK,
utf8_substr function will not be called by feed.php when the cache is
being sent.
I don't think above restrictions apply in my case, because I was the
only user and I tested less than a minute.
Actually, what I did was the following:
added an file-output to utf8_substr(), that appended the parsed html to
a file in /tmp/ whenever the function was called. Then I pointed my
browser
to feed.php and clicked reload several times - and got lots of
html-output
in the file. It was easily observable that it was the same output over
and over again, hence I think its not using caching.
I might be totally wrong, though, because of three reasons:
- I'm not sure if my cache is configured correctly
- I'm not sure if my hacking was correct
- utf8_substr() is called to estimate the page-length, I'm not sure
if that is always done (no matter if the page is cached or not), in
which case caching again had nothing to do with it.
