Jason Salas' WebLog

On-air and online: making people laugh, making people think, pissing people off

Sponsors

ASP.NET sites that kick ass

Pals with blogs

Podcasts I listen to

Before we called it AJAX...

Thr AJAX craze has got me thinking (so much so that it's disturbed my Java research).  I"ve been going back and re-reading a lot of the ASP.NET code samples I've collected, and I've noticed some having trace instances of asynchronous XMLHTTP calls via JavaScript.

Namely, I found an example in the wonderful "ASP.NET 1.1. Insider Solutions", in which the authors demonstrate how to create a slick staged page loading process.  It doesn't refer to the process by which it's doing what it does by any moniker, but it's all AJAX, baby.

Try out the example, check out the code, and give it a spin for yourself: http://www.daveandal.net/books/6744/loadpost/stagedloading.aspx

Posted: Aug 04 2005, 11:14 PM by guam-aspdev | with 3 comment(s)
Filed under: ,

Comments

Karl said:

Sorry, this page requires Internet Explorer 5 or higher

Even though AJAX doesn't specifically talk about cross-browser compatability, it's hard to call a an IE-only solution 'all AJAX'.
# August 4, 2005 8:40 AM

Kaniz said:

Thats the thing with AJAX - It's been around for /years/, or atleast the theory behind it. Its just with Google, and some guy on a blog slapping the AJAX name onto it, its become big and trendy - and its about time.

I remeber back in highschool doing a webpage for a graphic design class, and even though I wasnt using the XMLHTTPRequest object, but doing things though posts to hidden frames to dynamicaly update page content - same idea. It confused the hell out of everyone else in my class of "but..how did you load that without going to a new page/refreshing/etc?!"

Google did to 'AJAX' what Apple did to MP3s : Take something that had always been around, and do things with it in a way that made it massivly acceptable.

# August 4, 2005 11:39 AM

Matt Smith said:

From 2001 - 2003 I worked for a company where we had to display a lot of information to the user (>70K) but we kept getting complaints about pages being too slow. Research showed that a lot of these guys on 56K modems were only getting 8K - 10K connections. At the time, Firefox was not on the radar and Netscape was so crappy, that we had already decided to leverage the extended functionality of IE. I ran across a potential solution with 'XML Data Islands'. After a little learning curve of XML, XSL and XMLHTTPRequest we converted over several key pieces of functionality to only require 2-3K of data to build the page.
# August 4, 2005 12:24 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)