You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Andreas Hartmann <an...@apache.org> on 2005/04/08 11:10:12 UTC
Re: DO NOT REPLY [Bug 32840] - replace sitetree script with
one based on XMLHTTP
Josias Thoeny wrote:
> <snip/>
>
>>Before, the sitetree was generated from the sitetree.xml file.
>>But now, the SiteTreeGenerator uses the SiteTree object, currently
>>a DefaultSiteTree, which holds the sitetree in a DOM.
>>
>>Generating the sitetree from the DOM means heavy load on the DOM
>>itself and since the getLabels() method of SiteTreeNodeImpl access
>>the DOM in an asynchronous manner, it is most likely that the DOM
>>get corrupted (bug 33908).
>
>
> Concerning the performance, something else just came to my mind:
> It might make sense for the SiteTreeGenerator to implement the
> CacheableProcessingComponent interface. That way, its output could be
> cached by cocoon, which should increase the performance.
> The problem is how to know whether a cached result is still valid (i.e.
> how to implement the SourceValidity).
> Anyway, some profiling might be useful to see if this is really an
> issue.
Wow, you're already quite into the internals ...
I'm looking forward to your help in the design of 1.4 :)
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: DO NOT REPLY [Bug 32840] - replace sitetree script
withone based on XMLHTTP
Posted by jo...@wyona.com.
> Josias Thoeny wrote:
>> <snip/>
>>
>>>Before, the sitetree was generated from the sitetree.xml file.
>>>But now, the SiteTreeGenerator uses the SiteTree object, currently
>>>a DefaultSiteTree, which holds the sitetree in a DOM.
>>>
>>>Generating the sitetree from the DOM means heavy load on the DOM
>>>itself and since the getLabels() method of SiteTreeNodeImpl access
>>>the DOM in an asynchronous manner, it is most likely that the DOM
>>>get corrupted (bug 33908).
>>
>>
>> Concerning the performance, something else just came to my mind:
>> It might make sense for the SiteTreeGenerator to implement the
>> CacheableProcessingComponent interface. That way, its output could be
>> cached by cocoon, which should increase the performance.
>> The problem is how to know whether a cached result is still valid (i.e.
>> how to implement the SourceValidity).
>> Anyway, some profiling might be useful to see if this is really an
>> issue.
>
> Wow, you're already quite into the internals ...
> I'm looking forward to your help in the design of 1.4 :)
I certainly would like to help with 1.4, it's just lack of time...
I guess that's everyone's problem.
Currently I'm still working on the sitetree script replacement for 1.4,
problably that will be finished soon.
Josias
> -- Andreas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org