On Sun, Dec 13, 2009 at 04:41, wrote:
> Medium data set (2800 rows, 8 columns, cc. 750K XML size):
>XML: 2164 - 336 - 21
> JSON: 1817 - 21 - 21
>
> Conclusion: With this data size, the deference becomes noticable, the
> server side and communication overhead (XML is more verbose) is
, December 13, 2009 12:58:06 AM
Subject: Re: [qooxdoo-devel] XMLHttpRequest and POST messages and notification
Hi Balage,
Am 12.12.2009 um 23:16 schrieb balage42-qoox...@yahoo.com:
> PS: One interesting side-experience: The result is created in server
> side as a 2 dimensional array. From this
Hi Balage,
Am 12.12.2009 um 23:16 schrieb balage42-qoox...@yahoo.com:
> PS: One interesting side-experience: The result is created in server
> side as a 2 dimensional array. From this an XML is created, then
> posted to the client, where a DOM is built from it, iterated to
> create the arra
00
>Connection keep-alive
>Referer https://195.228.146.232/files/app/fullframe/index.html
>Cookie ****
>Authorization Basic aWZsb3c6dC5yYWIsYW4tdF82MCE=
>Pragma no-cache
>Cache-Control no-cache
>
>
>Post:
>--BOUNDARY-12345
>
>Content-D
Connectionkeep-alive Referer
> https://195.228.146.232/files/app/fullframe/index.htmlCookie
> AuthorizationBasic aWZsb3c6dC5yYWIsYW4tdF82MCE=Pragmano-cacheCache-Control
> no-cache
>
> *Post:*
> --BOUNDARY-12345
>
> Content-Disposition: form-data; name="FORM_ID"
#x27;string' ];
var eqData = [
['LNPS_CARRY_SURE', '1', '71.563', '71.563'],
['LNPS_PATIENT_TIME', '1', '710000.564', '71.564'],
['LNPS_AGAIN_PSM', '2',
On Fri, Dec 11, 2009 at 11:31, wrote:
> Hi!
>
> I've got ahead with the qx.io.remote.Request problem. In the archives I
> find information that even when I send my request as POST,
> the result comes as GET. I found that for each of my request, there is
> two message entry appears in the firebug
Hi!
I've got ahead with the qx.io.remote.Request problem. In the archives I
find information that even when I send my request as POST,
the result comes as GET. I found that for each of my request, there is
two message entry appears in the firebug log:
- the original POST message, which seemingl
