Hi Frederic, well Turbine is very clear about when tools are instantiated. Here is from the docs (although I assume you know that already)
# Scopes: # # global: tool is instantiated once and that instance is available # to all templates for all requests. Tool must be threadsafe. # # request: tool is instantiated once for each request (although the # PoolService is used to recycle instances). Tool need not # be threadsafe. # # session: tool is instantiated once for each user session, and is # stored in the user's temporary hashtable. Tool should be # threadsafe. # # authorized: tool is instantiated once for each user session once the # user logs in. After this, it is a normal session tool. # # persistent: tool is instantitated once for each user session once # the user logs in and is is stored in the user's permanent # hashtable. # This means for a logged in user the tool will be persisted # in the user's objectdata. Tool should be threadsafe and # Serializable. # # Defaults: none > tool.global.i18nMapper = fr.gicm.risque.operationnel.tool.I18nMapper > tool.global.mappingFormatter = > fr.gicm.risque.operationnel.tool.MappingFormatter > tool.global.formatter = fr.gicm.risque.operationnel.tool.Formatter > tool.global.confidentialityManager = > fr.gicm.risque.operationnel.tool.GestionnaireConfidentialite > tool.global.security = fr.gicm.risque.operationnel.tool.SecurityTool > tool.global.paginationManager = > fr.gicm.risque.operationnel.tool.GestionnairePagination > tool.global.gestionnaireLigne = > fr.gicm.risque.operationnel.tool.ligne.GestionnaireLigne > tool.global.gestionnaireEchelle = > fr.gicm.risque.operationnel.tool.echelle.GestionnaireEchelle > tool.global.gestionnaireArborescence = > fr.gicm.risque.operationnel.tool.arborescence.GestionnaireArborescence > tool.session.history=fr.gicm.risque.operationnel.tool.navigation.HistoriqueNavigation > tool.authorized.systemeInformation=fr.gicm.risque.operationnel.tool.SystemeInformationTool I would monitor / review the init() and refresh functions within these pulltools. You probably find your timelag inside those. Let me know what your investigations concluded. The performance hit must be somewhere inside those. -- Kind regards Juergen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
