I'm trying to migrate our application to SC8.2 and I ran into some issues with request queuing.
We are using our own custom server. SC communicates with it via json/XmlHttpRequest/POST.
In some cases SC generates queries like this:
Notice the irregularities in this request:
1. On the first line json attribute names are unquoted. If I understand correctly, json requires all attribute names to be quoted. Our json parser errors on this.
2. On the last line there is [object Object] in place of second request.
3. Also there is an empty string instead of third request. (At least that's what I think it is. Otherwise, there is an unnecessary comma.)
I'm seeing this behavior with both 8.2p (2012-01-17) and 8.3d (2012-01-17) builds.
I have made a testcase, but it requires a server to work. It doesn't work with clientOnly datasources. How can I make it useful? Or should I post it as is?
We are using our own custom server. SC communicates with it via json/XmlHttpRequest/POST.
In some cases SC generates queries like this:
Code:
12:31:08.723:MUP9:DEBUG:RPCManager:XMLHttpRequest POST to /service?isc_dataFormat=json contentType: application/json with body -->{ transaction: { transactionNum: 3, operations: [{
"dataSource":"dsStuff",
"operationType":"fetch",
"startRow":0,
"endRow":75,
"textMatchStyle":"substring",
"componentId":"isc_ListGrid_1",
"data":{
},
"oldValues":null
}, [object Object], ]}}<--
1. On the first line json attribute names are unquoted. If I understand correctly, json requires all attribute names to be quoted. Our json parser errors on this.
2. On the last line there is [object Object] in place of second request.
3. Also there is an empty string instead of third request. (At least that's what I think it is. Otherwise, there is an unnecessary comma.)
I'm seeing this behavior with both 8.2p (2012-01-17) and 8.3d (2012-01-17) builds.
I have made a testcase, but it requires a server to work. It doesn't work with clientOnly datasources. How can I make it useful? Or should I post it as is?
Comment