On 05/04/2011 11:24 AM, John Plevyak wrote:
The way the regex query works is that it scans the cache on disk. However,
it does not scan
the write aggregation buffer which is probably where you document is.
You might want to file that as a bug....
Also (and John probably knows this better than me), but I thought it
wasn't possible to use the existing APIs to write into the cache as an
"HTTP" object. At least that's what the documentation says. I.e. you can
cache your own content and retrieve those from the plugin, but it won't
be in a way that the HTTP core state machine would recognize. Afaik, it
has to do with the fact that there are actually two cache objects for
each HTTP object, and we don't expose how those two are linked to the
plugin APIs.
We really ought to have a way to do HTTP cache read / write APIs. Unless
of course the documentation is wrong, but I think I checked this before,
and unless the plugin "steals" some code from the core, and manage the
links between the two HTTP cache entries itself, it wouldn't work.
Cheers,
-- Leif
From the docs:
Note that the cache APIs differentiates between HTTP data and plugin
data. The cache
APIs do not allow you to write HTTP docs in the cache. You can only
write plugin specific
data which is a specific type of data which is different from the HTTP type.
