Hi Andreas, > >>> Maybe this is caused by a malfunctioning build optimization? Did you >>> take a look at the resulting js file (searching for callAsync or >>> 243)? >>> >> I tried to search for such numbers, but still didn't find anything >> reasonable. Strage is, that it seems, that it depends on how much >> data do >> I receive in one of last RPC calls. If I receive exactly same >> response, >> then type is always number1, but when I receive another amount of >> data, >> the number is always number2. It seems to me, that this "type >> number" is >> not hard-coded into source code. > > Did you try to output the parameters to callAsync before making the > call? That would tell you whether the problem is in your application > code or in the qooxdoo RPC code. Since there have been no previous > reports about such an issue, I guess the problem is somewhere in the > app code (and only triggered, for whatever reason, in the build > version).
What exactly do you mean by "output the parameters"? I put the params as param to callAsync, when I call it, I cannot debug the data I think. And before the call? before the call I just make: sess = new Object(); sess["type"]=string; sess["value"]=something; then rpcl.callAsync(function(),"send","method",sess); I don't know where in my code could the data be modified when its just few rows above the call :( But I'll be searching :) Martin ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
