> These are both indicative of the problem I stated elsewhere > recently: that the remote data model isn't asked to pre-fetch data > until it's needed for display. That's too late in many cases. The > request should be issued as soon as it becomes clear that data > _will_ be needed.
The problem that my patches address is delays in first request for data, as well as clearing old data before the control is shown. At present the control only lets requests go ahead when it is visible. > Your patches appear to cover up the problem more than fix it, if my > contention that the request for the data should be made earlier is > the correct solution to the problem. Would you agree? Realistically the patches will achieve the same performance as any new system as you can't request the data before you know you will need it! > Clearly a bunch of work needs to be done with the remote table > model to make it work better. Maybe applying your patches is the > right thing to do until there's time to do that work... Well, I agree with that (but I would say that, wouldn't I? - or MRDA - Mandy Rice Davies Applies - in another forum that I use - see http://en.wikipedia.org/wiki/Mandy_Rice-Davies ) Whatever the new design, it will still need to have these changes in place so that requests can be sent out as early as possible (and old data cleared before the control actually appears!) > Ping me next week and I'll try to look into this in more depth. OK. Hugh ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
