This content has been marked as final.
Show 3 replies
-
1. Re: Interface.js Permformance Question
wayofdragonster Feb 25, 2009 4:59 PM (in response to wayofdragonster)Can someone from the SEAM team comment on this? Do I have any reason to worry about performance?
-
2. Re: Interface.js Permformance Question
mocha Feb 25, 2009 10:57 PM (in response to wayofdragonster)You definitely want to minimize calls to interface.js. We've done a lot of tuning on our app, and interface.js is probably one of the bigger bottlenecks now. The reason is that each call to interface.js creates a conversation so the response for each request is relatively slow compared with a static javascript file. There's also no easy means of getting the browser to cache requests to interface.js unlike images and other static content. To minimise calls you can specify multiple components in a single call to interface.js:
<script type="text/javascript" src="#{basePath}/seam/resource/remoting/interface.js?customAction&customAction1&customAction2"></script>
-
3. Re: Interface.js Permformance Question
wayofdragonster Mar 7, 2009 7:40 AM (in response to wayofdragonster)Thanks alot for your tip! This is what i was worried about all along. Much appreciated!!! :)