> It was working for me well all the weeks :) > > But I am sitting on a 20Mbit connection at home ;) (and mhh, about > 100Mbit here at work ;))
<Homer>Mmmm, 20MBit...</Homer> > Please open a bug and suggest the timeout increasement there. See http://bugzilla.qooxdoo.org/show_bug.cgi?id=489 > Gzipping will also be an option. But a further split of the files > is IMHO not a good idea. It is already quite fine grained. Even > more files will result in slower performance because of the latency > which is also relevant. Note that the latency from here (UK) is actually quite good - for example, Bootstrap.js came in 140ms. And, once you have navigated round the tree just a little bit you will have requested all the base-class files anyway so there will be just one file requested (for the actual node you have opened). So there will be only a small extra delay from the latency up front, but a massively reduced delay from getting smaller files when clicking around the tree (e.g. in the UI section!) If you implemented a proper caching scheme using the web server facilities to check file dates, returning "304 - Not Modified" then there would be little or no delays in opening up the API viewer a second time (just the latency for those checks). Maybe I'll try another argument: when initially looking at AJAX packages, one of the key things we did was looking at the performance including download time. I think if you want to make qooxdoo look as good as you possibly can you must address all these issues (are you zipping the apiviewer script itself, for example?). It's a tough world out there in the AJAX wars, and only the best (or perceived best) will survive. You make qooxdoo look worse if there are performance improvements that you don't take advantage of. Potential users won't ever look past slow performance to the Wiki pages documenting ways of improving them, if they decide that qooxdoo isn't good enough in the first place on the basis of, for example, a slow (or broken!) api viewer. You should be aiming to get qooxdoo up on the top of the lists at sourceforge, like ZK - http://www.zkoss.org/ - it's at number 8 at the moment at http://sourceforge.net/top/mostactive.php?type=week . That appears in a summary email sent out to all Sourceforge users each month, and is a huge selling point ("if lots of people use it, it must be good"). qooxdoo is at 227 at the moment - maybe reduced in impact because you use your own bug tracker instead of the sourceforge one. Hugh ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
