Comments on: Dos and don’ts of AJAX

By: Posts Collection #1 « Dev – Blue solutions

Posts Collection #1 « Dev – Blue solutions — Sat, 13 Nov 2010 23:19:35 +0000

[...] Dos and don’ts of AJAX – fuelyourcoding.com [...]

By: Bernd Artmueller

Bernd Artmueller — Sun, 25 Apr 2010 21:02:34 +0000

can I check out a demo of this?I’m very interrested in your approuch :D

By: Larry Fulkman

Larry Fulkman — Sat, 12 Dec 2009 19:40:44 +0000

Nice contribution. Thanks.

By: cond0r

cond0r — Tue, 29 Sep 2009 09:43:17 +0000

Hy,

At “Case 1: Page loading” i can contradict you. (:P)

We can use a jquery history plugin, and after that back and forward buttons will work .
At part “user tries to copy the URL and send it to a friend”, I resolved it with anchors and jquery.

I made URL to look like this => http://www.example.com/#products/10/edit
after that, i made a split of document.location.hash, and after that AJAX request with results after split.

if you want a working example i can give it to you.
P.S: Sorry for my english.

By: Gaya Kessler

Gaya Kessler — Thu, 11 Jun 2009 09:11:34 +0000

Checking on the server side is more important. But checking on the client side prevents useless requests and improves the user experience. The reason you need to check on the server side is to prevent false data and access to protected files.

Thanks for the comment!

By: We Love Webdesign

We Love Webdesign — Tue, 09 Jun 2009 23:13:55 +0000

You pointed out the cons in the Case 1: Page loading, and i am totally agree with you on those. I have seen an example of overusing Ajax on an e-commerce website, there was no real page switch and for users it can be very disturbing, mostly if the loading response time is too long.

I agree with the fact using Ajax to load only small parts of information on the page is the right way. By overusing Ajax you’ll just kill the user experience.

(I am french, so sorry for my bad english). What i have understand on Case 2 is when using Ajax you need to check both client and server side, am i right ?

Thank you for this great article.

By: Gaya Kessler

Gaya Kessler — Mon, 11 May 2009 08:42:36 +0000

thanks for this comment f055.

Glad you agree with me in most of the cases.

About the JSON thing: I just think it’s the best one around at the moment. It’s very readable, but that’s something we have to accept for now

By: f055

f055 — Sat, 09 May 2009 22:54:46 +0000

Re 1: Very true, but difficult to achieve with complicated webapps that imitate desktop apps.

Re 2: Very true, and not only for AJAX. The basics are to absolutely always verify everything that comes to the server-side script. if you don’t do that you probably shouldn’t code webapps in the first place ;)

Re 4: JSON unfortunately ain’t the holy grail here either.. http://www.quirksmode.org/blog/archives/2005/12/the_ajax_respon.html
the advantages are obvious, and you have an API straight away, but the increase in JS code is enormous. As usual it’s a matter of application.

Nice article btw. Looking forward to next posts on AJAX.