Comments on: AJAX Gotchas http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/ News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com. Mon, 23 Nov 2009 05:23:27 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: Anonymous http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/comment-page-1/#comment-47202 Anonymous Wed, 23 Aug 2006 08:28:04 +0000 http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/#comment-47202 <strong><code><em>gfdgdfgfdg</em></code></strong> gfdgdfgfdg

]]> By: danwgreenfield http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/comment-page-1/#comment-23292 danwgreenfield Tue, 16 May 2006 04:54:54 +0000 http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/#comment-23292 Colin, I recently developed a store site that utilises a single page interface (<a href="http://www.techtoys.jp/store.php" rel="nofollow">http://www.techtoys.jp/store.php</a>). I did this because the main page contains two flash apps that load a lot of graphic images and I wanted the user to be able to move about the site without having the flash apps reload from the start when the page was reloaded, losing their position within the apps. Colin, I recently developed a store site that utilises a single page interface (http://www.techtoys.jp/store.php). I did this because the main page contains two flash apps that load a lot of graphic images and I wanted the user to be able to move about the site without having the flash apps reload from the start when the page was reloaded, losing their position within the apps.

]]> By: StianS http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/comment-page-1/#comment-23238 StianS Mon, 15 May 2006 15:27:05 +0000 http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/#comment-23238 @Colin: We have tables all over our site updating twice by the minute with prices from the power markets. When we used server-side scripting we sent out everything every time - HTML, CSS, JS and content. Now we only send content in an xml-file. It saves us tons of bandwidth and CPU. In that sort of environment it makes great sense! @Colin: We have tables all over our site updating twice by the minute with prices from the power markets. When we used server-side scripting we sent out everything every time – HTML, CSS, JS and content. Now we only send content in an xml-file. It saves us tons of bandwidth and CPU.

In that sort of environment it makes great sense!

]]> By: Qani http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/comment-page-1/#comment-22792 Qani Fri, 12 May 2006 18:56:55 +0000 http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/#comment-22792 Well Colin, I made an application where drop-down boxes would fill with entries from a database, depending on what was chosen in the previous drop-down box. And for that AJAX was very handy. I believe GMail is driven by AJAX as well. Well Colin, I made an application where drop-down boxes would fill with entries from a database, depending on what was chosen in the previous drop-down box. And for that AJAX was very handy.

I believe GMail is driven by AJAX as well.

]]> By: Colin http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/comment-page-1/#comment-22565 Colin Thu, 11 May 2006 06:52:33 +0000 http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/#comment-22565 Come on you ajax coders give me a good reason to develop using ajax. Point me to some sites that do something useful that couldnt be done more sensibly using php or any of a dozen other server side scripting languages. I just can't understand the rush to do things client side but then I've only been coding for 40 years so I can be rightly describes as a dinasaur. Come on you ajax coders give me a good reason to develop using ajax.

Point me to some sites that do something useful that couldnt be done more sensibly using php or any of a dozen other server side scripting languages.

I just can’t understand the rush to do things client side but then I’ve only been coding for 40 years so I can be rightly describes as a dinasaur.

]]> By: Aska http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/comment-page-1/#comment-22549 Aska Thu, 11 May 2006 03:24:25 +0000 http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/#comment-22549 I was not aware that "Ajax uses UTF-8" until now. Yet on a Big5 encoded website that I developed, the use of Ajax never caused any encoding issues (I have not utilised any encoding conversion techniques on the server side). Weird. I was not aware that “Ajax uses UTF-8″ until now. Yet on a Big5 encoded website that I developed, the use of Ajax never caused any encoding issues (I have not utilised any encoding conversion techniques on the server side). Weird.

]]> By: JaredWhite http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/comment-page-1/#comment-22496 JaredWhite Wed, 10 May 2006 16:56:13 +0000 http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/#comment-22496 We solved this problem in xajax (http://www.xajaxproject.org) by providing an automatic encoding conversion for incoming data (using either mb_string or iconv). A developer can just set the required encoding with one method call, and then xajax does the work under the hood. I prefer using UTF-8 anyway, though, and even if PHP doesn't totally support it yet, it works great if you're careful. We solved this problem in xajax (http://www.xajaxproject.org) by providing an automatic encoding conversion for incoming data (using either mb_string or iconv). A developer can just set the required encoding with one method call, and then xajax does the work under the hood.

I prefer using UTF-8 anyway, though, and even if PHP doesn’t totally support it yet, it works great if you’re careful.

]]> By: svanpoeck http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/comment-page-1/#comment-22459 svanpoeck Wed, 10 May 2006 09:40:53 +0000 http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/#comment-22459 IMO, XMLHTTPRequest *should* use the default page encoding *or* fully support unicode. This is *not* a feature AFAIK, it's a lack of it. IMO, XMLHTTPRequest *should* use the default page encoding *or* fully support unicode.

This is *not* a feature AFAIK, it’s a lack of it.

]]> By: z0s0 http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/comment-page-1/#comment-22436 z0s0 Wed, 10 May 2006 02:23:57 +0000 http://www.sitepoint.com/blogs/2006/05/10/ajax-gotchas/#comment-22436 Another good reason to switch to UTF-8 as the default for every page you serve! It is surprising, though, that XMLHTTPRequest uses UTF-8 and not the default page encoding. Another good reason to switch to UTF-8 as the default for every page you serve! It is surprising, though, that XMLHTTPRequest uses UTF-8 and not the default page encoding.

]]>