Comments on: Make Cross-Domain AJAX Requests with xdRequest

By: Abdiel Technologies

Abdiel Technologies — Wed, 11 Jan 2012 11:37:00 +0000

Hound is a site which search job for you accross the world …hound directly connect with the employers it means you apply directly to employers. hound does not allow any banner to promote there bussiness
it only provide what the employer wants it is basically a good site which give us a great utility.its a amazing site everyone should try this site … it help us to search job world wide n it is very convenient .
in this sit e you did not need to search more just type your qualification and in which city do u want to do job that’s it …….
executive job

By: GeekLad

GeekLad — Fri, 14 May 2010 19:28:40 +0000

Excellent, thanks for the tip! Are you interested in joining the project?

You could update the code in the repository if you're interested.

By: angl

angl — Fri, 14 May 2010 19:25:36 +0000

Hi again, debugging the library , I notice that attribute diagnostics no exists!
//attribute response.query.diagnostics no exists ?¿
//newresult.error = response.query.diagnostics.url[1]["http-status-message"];

Comment this line , works fine! but maybe is important to know which is the responsibility of this line.
Temporaly with this patch works fine! I hope this be useful for us.

By: GeekLad

GeekLad — Fri, 14 May 2010 14:28:40 +0000

Excellent, thanks for the tip! Are you interested in joining the project?
You could update the code in the repository if you're interested.

By: angl

angl — Fri, 14 May 2010 14:25:36 +0000

By: GeekLad

GeekLad — Thu, 13 May 2010 11:13:59 +0000

No, it will take some debugging to find the root of the problem. Time which
unfortunately I do not have.

By: angl

angl — Thu, 13 May 2010 10:20:39 +0000

Hi, yes, me too. The callback function is never call, do you know whats the cause? thnks in advance, is a great project!

By: GeekLad

GeekLad — Mon, 19 Apr 2010 21:14:54 +0000

Hmm, I'm not sure what broke it. It seems there's still a YQL response with
data coming back. I haven't seen any changes in the code since November.
Very odd indeed.

By: Gibbs

Gibbs — Mon, 19 Apr 2010 12:14:44 +0000

Hi – I have been using this script, and it all of a sudden stopped working. It also does not work on your demo page anymore. Do you have any idea why? It's a great script and I would like to continue to make use of it, but as I said it all of a sudden went dead.

By: GeekLad

GeekLad — Wed, 03 Feb 2010 23:42:17 +0000

In my demo app, you would have to click through and load enough pages for
your browser to trigger the limit.

By: GeekLad

GeekLad — Wed, 03 Feb 2010 23:41:42 +0000

The rate limit is on the client IP. Since everything takes place in the
browser window (the browser makes the calls to YQL), it would be based on
the browser's IP address.

By: Paul

Paul — Wed, 03 Feb 2010 22:58:50 +0000

As an example, in your demo app you created – what would need to happen in an hour for it to exceed the limit. Maybe that makes more sense as to what I am trying to ask! Thanks again.

By: Paul

Paul — Wed, 03 Feb 2010 22:46:01 +0000

Hi - awesome script! I have one question though that I'm not clear on. The rate limit per IP. let's say I put this script on my site, every time it is triggered in someone's browser, is that instance attributed to my site's IP or the users? Also - if this page is calling data from the same remote site (say CNN.com), will CNN.com be blocked to users of my site after 10000 page views? Of course only if this occurs in an hour. I'm just trying to figure out exactly what IP they are talking about, the user, the site that host's the .js file, or the site that is being "scraped"?

I hope I am making sense. Thanks again!

By: David Hopkins

David Hopkins — Mon, 16 Nov 2009 23:09:54 +0000

Thanks. No change though. I think the issue is with MooTools. I believe they have modified the Array object and I think that is causing the issue.

I have posted a detailed report in the MooTools forum. If someone can find out what's wrong I will let you know.

By: GeekLad

GeekLad — Mon, 16 Nov 2009 22:57:46 +0000

Hmm, I wonder if the version I have in the download section is an older
(damaged version). That for loop doesn't look as though it has been fixed
to work in Internet Exploder. Are you using IE? You may want to try
downloading the latest source in the trunk here:
http://xdrequest.googlecode.com/svn/trunk/xdReq...

By: David Hopkins

David Hopkins — Mon, 16 Nov 2009 22:07:07 +0000

It's a conflict with that in Mootools and the following in xdR:

for(cookie in cookiejar) {
if(cookiejar[cookie].match(url, this.secure())) {
outputCookies.push(cookiejar[cookie]);
}
}

Namely this bit:

cookiejar[cookie].match(…

It's saying that cookiejar[cookie] is an object when I guess it should be a string. However, if I bypass this, it just breaks.

I think it could be to do with some Mootools meddligns with the natives of JS, probably the array since that is what is conflicting in Moo. However, I am very rusty with JS. Maybe its time to moove on

By: GeekLad

GeekLad — Mon, 16 Nov 2009 21:41:24 +0000

Hmm, that's odd. I'm not very familiar with Mootools. I'm not sure why
xdRequest would cause Mootools to break.

By: David Hopkins

David Hopkins — Mon, 16 Nov 2009 21:25:42 +0000

I found out why it doesn't work in conjunction with Mootools. There is a line:

var natives = {'Array': Array, 'Date': Date, 'Function': Function, 'Number': Number, 'RegExp': RegExp, 'String': String};

Which is on line 96 for me. For some reason xdRequest won't run unless you remove the ['Array': Array] part of that object. I'm not sure exactly why this is an issue though.

By: David Hopkins

David Hopkins — Mon, 16 Nov 2009 21:07:22 +0000

Hi,

Excellent project. Been looking for something like this for a while. I am having problems using this in conjunction with other JS files though, namely MooTools and not getting any error output.

I think it may be some variable conflict. More project specific var and func names may help this issue.

By: GeekLad

GeekLad — Sun, 25 Oct 2009 13:32:07 +0000

The YQL servers will see the IP of the client. The remote site will see the
IP of the YQL servers. YQL also does pass along some headers that include
information about the client (for example, a header called X-Forwarded-For
that contains the IP address of the client).

Because of the security measures enforced by browsers, the only way you can
make remote requests 100% within a client is with services that provide an
API that provide JASONP responses. Otherwise, you have to use some sort of
proxy that will fetch the data for you and provide a JSONP response, as YQL
does. I think YQL is the best solution I've seen out there for doing this.