I have taken some steps with the javascript to help speed up screen handling some and moved all static functions out to files in /resources/jslib/utils.js or what have you... this did help some as there is about 800 lines or so of javascript.. and I'm not that poor of a programmer :) just a ton of logic to be accomplished on this page before can begin to send to the server.
mimicking the behavior of the old existing VB app has been the bane of my existence... but this is a good point to make in design I believe as well. the javascripts are cached and do help speed things up... it is the loading of the data into arrays that is what comprises the other 75% of the rendered velocity pages... and I did learn that it is best to take the hit at the beginning to read the arrays into memory from an onLoad() function for the whole page, rather than forcing the user to experience delays after the page has completely loaded. On Thu, 29 May 2003, David Wynter wrote: > Hi, > > A 800K HTML file over a 56K modem on a good line will take about 170 seconds > to download. If you have been clever and separated out the javascript as > static files and included them in the main page the browser can cache you > may improve on this for subsequent round trips to the pages that use these > javascripts. > > It sounds like it is mostly data that makes up the volume. I'd be thinking > about having data paging build into your screens, i.e. only show the first > 20-50 records for a screen with a button to fetch more if desired. Or using > a filter with a default value to restrict the number of records shown. > > Bear in mind that most government departments here in the U.K. and in > Australia consider 10 seconds a maximum download time for a HTML screen over > a 56K dial up connection, about 11KB page size. > > Regards > > David > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
