Jim Hunter-2 wrote: > > The biggest hit will be downloading the main JS file. Once the file is on > the client machine, things should run very quickly IF you have architected > your application correctly. In our app, the amount of data we are sending > per click is FAR LOWER then the amount of data that would be sent if you > were sending over a new web page. So our app is much faster on slower > connections then it used to be. It's all in your architecture and weather > or > not you take FULL advantage of AJAX. > > Jim > www.D4PHP.org <http://www.d4php.org/> > >
Yes, I realize that. Once the main js file is loaded everything is rosey. The problem is getting that first large file to load. I only load what is necessary in the main js file. My js file is about 650k and I do not see how it is ever going to be much smaller (compression is in the future). Except for the minimum amount of code to load the initial screen, all other code is brought in from the server as needed. Not just the data, but the javascript code to create the widgets. -- View this message in context: http://www.nabble.com/qooxdoo-on-dialup-connection-tf4767223.html#a13747748 Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
