Nice, quoting the part you want, how about I quote THIS line:


Stands to reason that he wants ALL the same BUT one thing changed. How can he have the same information if the ONLY thing you display is different?

If he's passing all the details on to an end user, then he wants the whole stream of info for api, the way you suggest means he'd have to make a seperate script and page for each of the details. If he wanted to just pull one at a time he could have just read from source and had a single trigger somewhat like yours is. It sounds like he wants the whole set of information sent though.

Also I did something like this as a script on my own site, because javascript can't pull from another site (cross site scripting limitations) so I couldn't pull DeepBit stats, what I did was a passthrough that just grabbed the json through php, then returned the whole json. Then my html could locally call the stat page and have a json array to parse cheap and easy in a few lines, from there you can easily change the php and javascript request with a GET parameter to limit the returned values to a single variable.