I am using qooxdoo-0.8.3, along with web2py as my backend. My web
server and client are on the same network/domain. I have observer that
depending on the URL provided to the RPC object and whether I set
crossDomain, I get weird behavior even when running the software from
the web server itself. I have found the following:
web server / json-rpc service host = server.domain.com / server
client resolves to client.domain.com (they are both in the same domain)
1.
-------
setting
var rpc = new
qx.io.remote.Rpc("http://server.domain.com/app/controller/call/jsonrpc";);
rpc.setCrossDomain(false);
- connecting to http://server/qxapp/source from the client produces
"Transport error 0: Unknown status code"
- connecting to http://server/qxapp/source from the server produces
"Transport error 0: Unknown status code"
- connecting to http://server.domain.com/qxapp/source from the client
produces a positive response from the service
- connecting to http://server.domain.com/qxapp/source from the server
produces a positive response from the service
2.
-------
setting
var rpc = new qx.io.remote.Rpc("http://server/app/controller/call/jsonrpc";);
rpc.setCrossDomain(false);
- connecting to http://server/qxapp/source from the client produces
"Local error 1: Local time-out expired"
- connecting to http://server/qxapp/source from the server produces
"Local error 1: Local time-out expired"
- connecting to http://server.domain.com/qxapp/source from the client
produces "Transport error 0: Unknown status code"
- connecting to http://server.domain.com/qxapp/source from the server
produces "Transport error 0: Unknown status code"
3.
-------
setting
var rpc = new
qx.io.remote.Rpc("http://server.domain.com/app/controller/call/jsonrpc";);
rpc.setCrossDomain(true);
- connecting to http://server/qxapp/source from the client produces
"Local error 1: Local time-out expired"
- connecting to http://server/qxapp/source from the server produces
"Local error 1: Local time-out expired"
- connecting to http://server.domain.com/qxapp/source from the client
produces "Local error 1: Local time-out expired"
- connecting to http://server.domain.com/qxapp/source from the server
produces "Local error 1: Local time-out expired"
4.
-------
setting
var rpc = new qx.io.remote.Rpc("http://server/app/controller/call/jsonrpc";);
rpc.setCrossDomain(true);
- connecting to http://server/qxapp/source from the client produces
"Local error 1: Local time-out expired"
- connecting to http://server/qxapp/source from the server produces
"Local error 1: Local time-out expired"
- connecting to http://server.domain.com/qxapp/source from the client
produces "Local error 1: Local time-out expired"
- connecting to http://server.domain.com/qxapp/source from the server
produces "Local error 1: Local time-out expired"
5.
-------
setting
var rpc = new qx.io.remote.Rpc("http://server/app/controller/call/jsonrpc";);
** do not call rpc.setCrossDomain()
- connecting to http://server/qxapp/source from the client produces a
positive response from the service
- connecting to http://server/qxapp/source from the server produces a
positive response from the service
- connecting to http://server.domain.com/qxapp/source from the client
produces "Transport error 0: Unknown status code"
- connecting to http://server.domain.com/qxapp/source from the server
produces "Transport error 0: Unknown status code"
6.
-------
setting
var rpc = new
qx.io.remote.Rpc("http://server.domain.com/app/controller/call/jsonrpc";);
** do not call rpc.setCrossDomain()
- connecting to http://server/qxapp/source from the client produces
"Transport error 0: Unknown status code"
- connecting to http://server/qxapp/source from the server produces
"Transport error 0: Unknown status code"
- connecting to http://server.domain.com/qxapp/source from the client
produces a positive response from the service
- connecting to http://server.domain.com/qxapp/source from the server
produces a positive response from the service
I would think that at the very least, running the code from the server
would always produce positive results. That does not appear to be the
case, at least in my setup. Can anyone shed some light?
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
