cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Baptiste Quenot (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COCOON-1681) Generator "directory": Caching too much
Date Wed, 25 Jan 2006 09:29:10 GMT
    [ http://issues.apache.org/jira/browse/COCOON-1681?page=comments#action_12363933 ] 

Jean-Baptiste Quenot commented on COCOON-1681:
----------------------------------------------

Disabling the expiry check is not an option, because it would mean that we make a stat() system
call for every generated file everytime the generator is invoked.  It would be better to understand
why isValid() is called twice by providing the two stack frames (copy/paste from the debugger).
 The first isValid() call returning INVALID should trigger the removal of the cached response.

> Generator "directory": Caching too much
> ---------------------------------------
>
>          Key: COCOON-1681
>          URL: http://issues.apache.org/jira/browse/COCOON-1681
>      Project: Cocoon
>         Type: Bug
>   Components: * Cocoon Core
>     Versions: 2.1.8, 2.1.7
>     Reporter: Antonio Fiol
>     Assignee: Cocoon Developers Team

>
> In some cases, an update to the directory is not detected by the DirectoryGenerator.
> Debugging the issue, I discovered that isValid() is called twice on the same DirValidity,
but it returns different values (-1 the first time, 1 the second time).
> Apparently, the reason for the inconsistency would be solved by removing the first of
the two lines that update the expiry time in the isValid() method in DirValidity, but I am
not sure whether this could cause problems in other places.
> A possibility would be that a DirValidity stores the fact that it already detected it
is invalid, and is changed so that it always return -1. But... Are DirValidity objects reused?
Could this change cause problems? I have not tested, so I don't know.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message