On Tue, Jan 12, 2010 at 12:12, Mustafa Sak <i...@saksys.de> wrote: > Thank you for your advise. But my indexes are allready set. I am > getting the request in less then 2 seconds. I think the virtual > scrollbar positioning is the problem. But i dont realy know. >
The remote table model sends your backend an explicit set of rows to be returned. You need to be sure to return only those rows. If used properly, you should have no excessive time spent in Javascript that would cause a timeout, and many people are using it, so it is known to work both properly and well. (That's not to say that there couldn't be a bug, but I wouldn't lean towards that assumption quite yet.) It's possible that your client-side code is getting stuck in some kind of loop that's causing the problem. In any case, the size of the database on server side should have no impact on the display of a subset of database rows at the client side, other than the query time which you've stated is short. Derrell
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
