[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Fenfire-dev] about caching and testing
From: |
Tuomas Lukka |
Subject: |
Re: [Fenfire-dev] about caching and testing |
Date: |
Sun, 14 Sep 2003 12:14:15 +0300 |
User-agent: |
Mutt/1.5.4i |
On Sat, Sep 13, 2003 at 08:10:47AM +0300, Asko Soukka wrote:
> I fixed FenMM (org.fenfire.demo.mm) to use the new api, but got a
> problem with caching: usually the content of nodes didn't update at
> all, sometimes the content updated while editing, but after I moved to
> an another node, the node returned to show the old content. I wonder,
> if someone can the problem in the following code. Mudyc said that
> there is no need for explicit freeing of the changed node from the
> cache.
Yes, there certainly shouldn't be.
The accursed nodes come from a different cache so changing back is what
will happen if that cache is not getting updated...
Hmm, your having the ContentFunction cache of size 1 may be tickling some bug...
... AHH, found it. SuperFunctional's Cache entry has
public void chg() {
if(closed) {
p("chg closed entry");
return;
}
super.chg();
}
and this is certainly what's happening here, I think. Are you getting "chg
closed entry"
messages?
The point is that it *is* ok for a closed entry to get a chg() signal... will
make a test and fix
ASAP (you can, of course, help if you want).
Tuomas