On Mon, Sep 7, 2009 at 12:59 AM, skar<[email protected]> wrote: > Matthew Curry wrote: >> var req = new >> qx.io.remote.Request("http://localhost:4242/getfeeds";, "GET", >> "text/plain"); >> > If your qooxdoo app resides on the same server as > "http://localhost:4242";, then you can just send the relative URL like: >> var req = new >> qx.io.remote.Request("/getfeeds", "GET", >> "text/plain"); > That way, you needn't hard code your server address and also it might > not trigger any cross domain restriction policy of the browser or > qooxdoo itself. > > cheers, > skar. >
That's true. I'm developing my qooxdoo app from the filesystem directly. In other words, I'm opening source/index.html directory, no server, so any http request appears as 'cross domain' to qooxdoo. However, putting the 'source' directory in of my qooxdoo project behind the webserver doesn't work, I think because it's trying to link with the qooxdoo .js files in the qooxdoo directory... argh. Why doesn't qooxdoo's create-application script make a local copy of all of qooxdoo's .js files in the project directory and link against that copy? I'm not sure I like the dependency on where I happened to unpack qooxdoo's tarball, and besides, disk space is cheap. I mean I think all I have to change is the index.html in source/ and I could do the copy myself, just a little bit annoying that a created project isn't self-contained. Even still though, any thoughts as to the original problem, that Requests are timing out inexplicably? ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
