On 01/22/2013 03:09 PM, Peter Schneider wrote:
> 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 ...
So you requesting getRowCount multiple times, the row count effectively
changes on the server, but the changed count is not available on the
client, is that right?! And you don't see subsequent getRowCount calls
being translated into network requests that actually reach your server,
right?!
> I can not 100% re-create this issue I am seeing here with the playground
> example, unfortunately.
Ok, and the issue here is that the rowCount with the demo.qooxdoo.org
backend doesn't change, so it's hard to verify that the data you are
getting is old, right?! But if I understand you correctly, the requests
aren't even been issued to the server, and *this* is easily verifiable
(albeit not in the Playground sample directly) by looking into the
network layer, independent of the server returning the same data or not.
>
> 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!
The interesting question is whether our IO layer is issuing XHR requests
at all. You should be able to tell this from e.g. the Network tab of
your browser console, or using some qx.io debug settings.
But given the fact that your simple change has such a profund effect,
you might open a bug for it so we can have a deeper look. But as a
prerequisite you need to devise a Playground example that reliably
reproduces the issue in your environment, e.g. by just issuing
getRowCount calls that don't get translated into network requests
eventually. Make note in the bug that the problem is not visible in the
Playground GUI, but only when looking into the network layer and looking
for the missing request. Make also a note that the issue persists even
when you clear the browser cache after every getRowCount call (provided,
of course, all of the previous proves true). Without a setup that lets
us reproduce the issue reliably we cannot do much.
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
