Skip to main content

Exploiting Ajax

This XmlHttpRequest thingie (aka Ajax as pointed out by Rakesh), is getting INTO my blood. Can't help it, the features provided are really good.

Gone are the days when we required to call form.submit(), everytime we needed to validate simple items, etc. etc. Whew, just thnking about the possibilities screws up my mind. Was checking out as to how others have used this object, and came up with this small list,

Seeing the list, makes me think, maybe i should shift to google :D

Then i came across this site, which talks about Usability Guidelines for XmlHttpRequest. Wow, that's something new. Anyway checked it out and found that his examples and mis-examples are somethings really worth reading about.

Further if you really dont know what i am speaking about, this site of apple's is a great explanation of the object and it's functionalities.

I guess i better sign off before you get bored of XmlHttpRequest. Also need to get back to working on Client CallBack, yeah, u guessed it right, the XmlHttpRequest object provided by ASP.NET 2.0 (codename Whidbey)

Comments

Post a Comment

Popular posts from this blog

B.O.F.H.

Was browsing the net, and found some old link to BOFH. Not sure as to how many used to read PCQuest some time back when it used to come, but i remember reading them, with of course re-reads and re-re,etc...i can go on you know. Anyway, it's about a system operator who is bugged by no-brainers asking silly computer related queries, and this guy repling with wierd answers. I had never known the origin of this character, until i saw this . Anyway for those who have never read BOFH, here are two of them.
Post a Comment
Read more

So you have your website deployed in PROD ... now what ??

Posting on behalf of Usr.Web.Speed - My previous job had been to architect and develop websites for various customers. During that time my team and I have architected and developed various web applications mainly for enterprises. (But below info is not restricted to enterprises) Other than the usual development and testing tasks involved, our focus area was to abide by multiple SLAs. One of the primary SLAs was to provide the users of our websites a very low (usually subsecond) response time (or page load time). To adhere to this SLA, we did multiple activities, in code, process as well as infrastructure. These include (but not limit to) - Using best practices including (http://developer.yahoo.com/performance/rules.html) Determining the optimum number of calls to the databases, open connections, etc. Providing the fastest mechanisms to download associated content (such as stylesheets, JS files, etc. over CDN) And debugging the reason for the slowness of the websites, when ...
Post a Comment
Read more