The remote model is not responsible for cached or even not cached requests. Its only caching data for internal propose. May be someone else in the mailing list can advise you to solve this issue.
Mustafa Sak Applications & Integration 1&1 Internet AG Ernst-Frey-Straße 10 DE-76135 Karlsruhe -----Ursprüngliche Nachricht----- Von: Peter Schneider [mailto:[email protected]] Gesendet: Dienstag, 22. Januar 2013 15:10 An: qooxdoo Development Betreff: Re: [qooxdoo-devel] qx.ui.table.model.Remote::reloadData() issue in 1.2.x branch Hello Thomas, thanks for the info. Caching is something that definitely *does* change the behavior, but in my case it's not the problem. My application just only requests a getRowCount (RPC) and no futher getRowData ... I can not 100% re-create this issue I am seeing here with the playground example, unfortunately. But what I see is, that I can 'fix' my "1.2.1 branch" version by using this: <code> if (this._firstLoadingBlock != -1) { // ... } // Force clearing row cache, because of reloading data. this._clearCache = true; // ... </code> instead of (the current) <code> if (this._firstLoadingBlock != -1) { // ... // Force clearing row cache, because of reloading data. this._clearCache = true; } // ... </code> in qx.ui.table.model.Remote#reloadData() I can not see how this effects the browsers cache behavior...it definitely changes the "updateData()" behavior on my end here! Regards, Peter > > Looking at the network packet level, pressing the "Reload" button does > *not* immediately result in a network request to the server, which is > on my machine due to browser caching (I'm looking at Chrome currently). > Clearing the browser cache after each reload will force network > requests going out to the server, fetching new data. Without that, > data with a seen URL is fetched from browser cache. > > So looking at, say, the first 15 records in the table they won't > change at all between "Reload" presses. If you then start to scroll, > further records get shown. Depending on whether you have looked at > those rows before you get the old data, or you are looking at row > indecies for the first time then fresh data is retreived from the > server, showing new time stamps. > > So I believe the XHR requests are issued from JS code fine, but the > result that is displayed depends on browser cache behaviour. > > T. ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
