Hi Stefan,
thanks for your answer. Find my comments below:
Am Donnerstag 27 Januar 2011, 14:14:07 schrieb Stefan Volbers:
> Hi Cajus,
>
> > TypeError: 'response.id' ist Null oder kein Objekt
>
> seems like you want the result object to have an "id" property.
> Which, according to wireshark,
>
> > {"error": null, "result": "admin", "id": 2}
>
> is not there, as the result object is only an "admin" string.
Who does request the .id property? My code does not. It is reproducible by
that simple application snippet on qx side:
8<-----------------
// Create a button
var button1 = new qx.ui.form.Button("First Button", "rpctest/test.png");
// Document is the application root
var doc = this.getRoot();
// Add button to document at fixed coordinates
doc.add(button1, {left: 100, top: 50});
// Add an event listener
var rpc = new qx.io.remote.Rpc('/rpc');
button1.addListener("execute", function(e) {
rpc.callAsync(function(result, exc){
if(exc){
new qx.core.Object().debug("Fehler!");
qx.dev.Debug.debugObject(exc);
}else{
new qx.core.Object().debug("Ok!");
qx.dev.Debug.debugObject(result);
}
},'login','very','secret');
});
8<-----------------
Please just ignore that it's another method like in the dump below. That
snippet works in FF, Chrome and Opera, but is talking about that response.id
thingie in IE. Same for sync calls.
> BTW, I'd consider it a bit overkill to use wireshark for RPC debugging -
> you use Firebug on Firefox at least? If so, does it show the same RPC
> result? AND, is the RPC POST/GET query the same, no matter if you use IE
> or another browser?
I use wireshark because I don't know any tools that show the relevant
information in IE. The build in stuff sucks. If I compare the communication
between Firefox and IE, they're the same. So: yes, the RPC results sets in IE
and Firefox get are identical.
> Speaking of which, which RPC backend do you use - does it need any
> special treatment/configuration?
It's a wsgi python backend with jsonrpc logic. But as it works with other
browsers, I don't think that this one has problems. I'm always seeing 200 OK
on the RPC side and the result codes sent are identically for IE and FF.
> Is the RPC a crossDomain one, or using BasicHTTPAuth or such we should
> know?
No cross domain communication: the application is in /, the backend in /rpc.
> If this isn't of any help, maybe you wanna post the RPC call and/or the
> result handler, so we might have a look into that.
-Cajus
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
