AJAX in the rasx() Context

Okay, I’ve built my first small sketch of an AJAX application and have lived to write about it. I lost last Saturday morning fruggin’ with those bits but it was not as bad as previously thought. From jump—the premiere leap into this madness—it must be mentioned that AJAX is popular with the “tech” news media because Google uses the term AJAX—and Google’s stock price is all off into crazy dollars that make people holler AJAX! So it is sort of annoying to hear Microsoft employees—like Scott Isaacs—kind of ‘whine’ about inventing the dynamic interface technology Google ‘made’ popular. It’s like hearing me talk about how Europe founded its civilizations from the death of African ones then all but destroyed the evidence so ugly teenaged millionaires can pretend it’s a Whiz Kid World at the natural world’s expense. You “dudes” don’t want to hear all that “crap.” Let’s keep it real! Here are a few AJAX links:

What I needed to hear loud and clear in an introduction to AJAX are what can be seen a limitations associated with security implementations and AJAX. There are no significant security concerns with AJAX when you request XML from the same domain as the call. However, when you call out of the zone the limits pop up. The workaround I have so far is to send the client request to the server and have the server make the request again. This makes two requests out of one. There must be something better—apart from signing my scripts and depending on Java technology for authentication in browsers like Firefox.

Eventually these AJAX designs will change the “home” pages of kintespace.com and SonghaySystem.com. These pages will automatically update, reading RSS feeds from multiple sources using AJAX and Scott Isaacs’ innovations. To put the last two sentences in buzz-words, an AJAX RSS “aggregator” will be built for SonghaySystem.com and kintespace.com.

rasx()