Stefano Mazzocchi wrote: >Sylvain Wallez wrote: > <snip/>
>>There's the ServletTargetFactory that logs to the servlet container. It >>is declared in logkit.xconf and was used up to recently to log all >>errors to the engine's log >> >Is this documented? > The LogTarget is in LogKit and the LogTargetFactory is in Excalibur. >>About clustering, we have a component that I think won't work in >>clustered environment : the FragmentExtractor/Generator. It grabs on the >>fly parts of a document and keeps them in memory for servicing by >>requests that follow the current one. In a clustered environment, it is >>very likely that those requests are served by another computer in the >>cluster, and thus the extracted fragments won't be found. >> > >Damn, that's right. BTW, I've always considered it to be a hack, but >never found an objective evidence for it: I think you did :) > Maybe a hack, but a nice hack ! I was really impressed by this idea which helps a lot to serve documents that have to be decomposed in several subdocuments because of the limitations of http. >I think we need to seriously consider removing it and provide a better >alternative is the functionality is used (I never found the need for it >myself, but others might have) > >What do you think? > Instead of removing is abruptly, it would be better to add a flashy warning about clustering issues in the javadocs and plan a rewrite in the todo list. >>A solution could be to store these fragments in the servlet session : >> I also thought of using your nice XMLCompiler to store fragments instead of building a DOM to speed up things. I volunteer for that but won't be able to do it quickly. So no problem if someone else wants to do it ! Sylvain -- Sylvain Wallez Anyware Technologies - http://www.anyware-tech.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
