> For now I'm thinking about a class, similar to Request.HTML that gets > stuff into an iframe, loads it, then returns the content into > onSuccess and removes the iFrame? Not AJAX, but might work - would > that make sense?
If I was forced to code it I would have the request be a normal request and then add onRequest and onComplete events. onRequest I'd create an iframe element with a src pointing to a file, that, on the server side (assuming php) is just a big long sleep(), like sleep(10000000000). That should force the browser into a "loading state". And then onComplete destroy the iframe element. I love to beat dead horses. A simple indicator by the link or over the content that's updating is enough ...
