Hi.

I have tried the dojo inputSuggest in a few applications, never had
problems with slow loading times. Now with server side state saving,
as you have said, every needed dojo class is loaded, and this results
in many js files.

I've studied it a bit closer. Here's a small log of what's actually loaded from the server:

NO.      Duration(s)  Size   URL
1 1,031 s 64866 record/edit.html 2 0,014 s 773 script/widget/__package__.js 3 0,141 s 6280 script/xml/Parse.js 4 0,249 s 14957 script/widget/Widget.js 5 0,203 s 9668 script/widget/Manager.js 6 0,061 s 10765 script/widget/Parse.js 7 0,094 s 17584 script/widget/DomWidget.js 8 0,000 s 598 script/uri/__package__.js 9 0,078 s 6209 script/widget/HtmlWidget.js 10 0,031 s 5865 script/widget/ComboBox.js 11 0,124 s 12611 script/widget/html/ComboBox.js 12 0,000 s 718 script/io/__package__.js 13 0,000 s 3328 script/io/cookie.js 14 0,046 s 6045 script/widget/html/stabile.js 15 0,094 s 5829 script/widget/Wizard.js 16 0,000 s 712 script/widget/LayoutPane.js 17 0,109 s 11399 script/widget/html/LayoutPane.js 18 0,031 s 574 script/widget/Container.js 19 0,000 s 1393 script/widget/html/Container.js 20 0,015 s 2298 script/collections/ArrayList.js 21 0,000 s 2087 script/collections/Collections.js

(Note: this page was already accessed before, so all of the scripts were already loaded once).

It's 20 scripts of more than 100K, loaded in ~1 sec. Could this be somehow optimized?

Bye.
/lexi

Reply via email to