But it would get tricky to send the request to another site in this case, given the logic flow I had set up. But…
This would seem like the perfect time to roll out some AJAX implementation. This might mean that, JS code could seek out the server and parsed RSS content, and display it to a specified part of a page. But let’s say, it got no response… well, perhaps the JS could contain 3 or 5 alternative sites that ti could send the same parameter string to… then it could keep trying. And there should be some way to put a status indicator in the page’s place where the outpit goes.
I’ve only done minimal AJAX but it seems, like the right way to go. Anyone have any thoughts??
The downside is it would take a bit more cutting and pasting, as AJAX calls for a suite of JS code that needs to be in a web page’s content, or linked to a library somewhere. I worry about something that might be more robust functional wise, versus something that might be more challenging to use.
The post "Sprinkle Some Ajax into Feed2JS?" was originally zapped with 10,000 volts and declared "It's ALIVE" by Dr. Frankenstein at CogDogBlog (http://cogdogblog.com/2006/07/sprinkle-some-ajax-into-feed2js/) on July 4, 2006.