Thanks for the reply. Perhaps it is that I just don't understand what this setting is supposed to do? I assumed that this setting was used to remove the nocache param from my remote.Request calls, is this not correct? The server that I am sending my requests to is a REST server that has specific things that tit looks for on the URL and adding the nocache=32423234 is causing it to send back errors and not execute the request. I am working with the CouchDB database, if that sounds familiar to you.
Thanks, Jim On Sat, Feb 5, 2011 at 1:51 AM, thron7 <[email protected]> wrote: > Jim, > > are you sure you're looking at the right problem?! Your config snippet > looks right, and I'm confident you removed any comment signs around the > jobs section. > > The thing is, add-nocache-param *is* false for the build version by > default, so you are not actually providing anything new here. And unless > you are using parts, there is only one script file to load in the build > version anyway, and you should see just a single .js file being loaded in > Firebug's net tab. Does this single file have a 'nocache' parameter? Are > you sure you are looking at your build version? Is it possibly the > *source* version you want to tweak (then switch to "source-script" in your > config)? > > T. > > >> I need to remove the nocache param from the URL of my outgoing >> requests but making the needed change does not seem to produce the >> desired results. Here is the added part to the config.json file, the >> rest is what is created when you create a new project. I am using the >> latest SDK build. >> >> "jobs" : { >> "build-script" : { >> "compile-options" : { >> "uris" : { >> "add-nocache-param" : false >> } >> } >> } >> } >> >> >> Does anyone see anything obvious? If not, what might be going wrong here? >> >> Thanks, >> Jim >> >> ------------------------------------------------------------------------------ >> The modern datacenter depends on network connectivity to access resources >> and provide services. The best practices for maximizing a physical >> server's >> connectivity to a physical network are well understood - see how these >> rules translate into the virtual world? >> http://p.sf.net/sfu/oracle-sfdevnlfb >> _______________________________________________ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> >> > > > > ------------------------------------------------------------------------------ > The modern datacenter depends on network connectivity to access resources > and provide services. The best practices for maximizing a physical server's > connectivity to a physical network are well understood - see how these > rules translate into the virtual world? > http://p.sf.net/sfu/oracle-sfdevnlfb > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
