cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <joerg.heini...@gmx.de>
Subject Re: [jira] Updated: (COCOON-1977) Unsynchronized access to HashMap in ResourceReader
Date Fri, 05 Jan 2007 00:35:14 GMT
On 04.01.2007 22:13, Jörg Heinicke (JIRA) wrote:

> Jörg Heinicke updated COCOON-1977:
> ----------------------------------
> 
>     Affects Version/s: 2.2-dev (Current SVN)
> 
> I'm wondering what this "caching" does buy us at all? Can somebody
> tell in which cases the reader is really faster? From what I understand
> in those cases, when one request.getRequestURI() resolves to different
> inputSources. I'd remove documents and quickTest completely.

Found the original commit [1] and the thread where it was discussed 
before [2]. But I can not really see how it helps to optimize and 
whether it is an optimization at all.

With the document list but without quickTest it would behave differently 
if the requestURI would lead to a different InputSource - I wonder if 
this can happen. Without the document list it would not behave 
differently than now I think as no check against a former 
InputSource.getURI() can be done. So what's up with that stuff? Is that 
still valid?

Regards
Jörg

PS: Happy New Year btw. :)

[1] http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104019898011748&w=4
[2] http://marc.theaimsgroup.com/?t=102854688200001&r=1&w=4

Mime
View raw message