I've been wondering for a long time how caching worked (from a
high-level), and which of the tables are considered "caching" tables,
and which aren't. I assumed that both messages and cache were related
to the cache but either that is not the case or the caching flag isn't
being properly adhered to.
Can anyone shed any clarity on this?
-Charles
Mark Edwards wrote:
Can you give a very rough outline of the flow involved in listing a
particular message? It seems like more is happening than should be
happening for this relatively simple operation.
I do see that my "messages" table is filling up with messages, even
though I have caching turned off. My "cache" table remains empty
though. If caching is off, should Roundcube bother storing any info
about any messages at all?
On Feb 24, 2006, at 1:22 PM, Sjon wrote:
If the caching-mechanism of Roundcube decreases the performance of the
application instead of increasing it; it might be a good idea to
improve the caching-mechanism! :) I hope to be able to spend some time
on it this weekend; any additional information on the implementation
and ideas behind Roundcube current or preferred way of caching would
be appreciated
--
Mark Edwards
