Sounds fair enough. The best way to get something like this implemented though 
is
to provide a patch for the fixes and attach it to the JIRA ticket.

james


On Fri Jul 27  9:05 , Felipe Rodrigues <[EMAIL PROTECTED]> sent:

>
>Hi guys,
>
>I'm thinking about open an issue to make put parseWidgets: false on djConfig
>initial load. This would improve the performance so much. 
>The fact is that dojo walk through each DOM node in a document looking for
>widgets to parse, so it makes the footprint very slow.
>The solution is to tell to dojo what are our widget, based on widget id. A
>simple solution would be put a line in each ftl template to render some dojo
>widget. Something like that in FTL:
>
>
>  
>    delay="${parameters.delay?c}"
>  
>  
>    updateFreq="${parameters.updateFreq?c}"
>  
>  
>    autoStart="${parameters.autoStart?string?html}"
>  
>  
>    startTimerListenTopics="${parameters.startTimerListenTopics?html}"
>  
>  
>    stopTimerListenTopics="${parameters.stopTimerListenTopics?html}"
>  
>  
>    refreshOnShow="${parameters.refreshOnShow?string?html}"
>  
>  
>    scriptSeparation="${parameters.separateScripts?string?html}"
>  
>  
>  
>>
>djConfig.searchIds.push("${parameters.id}");
>
>From what I've seen this would be a little change that would make us improve
>the performance of Struts2.
>
>What do you think guys?
>
>Felipe
>-- 
>View this message in context:
http://www.nabble.com/-S2--parseWidgets-should-be-false-for-better-performance%21-tf4157653.html#a11828783
>Sent from the Struts - Dev mailing list archive at Nabble.com.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to