<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Clientcide (Formerly CNET's Clientside) &#187; Ajax</title>
	<atom:link href="http://www.clientcide.com/category/code-snippets/ajax/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.clientcide.com</link>
	<description>Making stuff work on the other side of the request.</description>
	<lastBuildDate>Tue, 20 Jul 2010 20:40:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>New Plugin: Request.Queue</title>
		<link>http://www.clientcide.com/code-snippets/ajax/new-plugin-requestqueue/</link>
		<comments>http://www.clientcide.com/code-snippets/ajax/new-plugin-requestqueue/#comments</comments>
		<pubDate>Tue, 02 Dec 2008 01:20:10 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Code Releases]]></category>

		<guid isPermaLink="false">http://www.clientcide.com/?p=546</guid>
		<description><![CDATA[The MooTools Request class gives us the option to link together requests so that with a single instance of the class, if you&#8217;ve got a request that&#8217;s running you can &#8217;stack up&#8217; any new send requests so that they occur one after the other.
This is convenient, but what if you have numerous instances of Request [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/ajax/new-plugin-requestqueue/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Preventing Ajax Request Caching in MooTools &#8211; introducing Request.NoCache</title>
		<link>http://www.clientcide.com/code-snippets/ajax/preventing-ajax-request-caching-in-mootools-introducing-requestnocache/</link>
		<comments>http://www.clientcide.com/code-snippets/ajax/preventing-ajax-request-caching-in-mootools-introducing-requestnocache/#comments</comments>
		<pubDate>Thu, 20 Nov 2008 22:49:07 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Code Releases]]></category>

		<guid isPermaLink="false">http://www.clientcide.com/?p=506</guid>
		<description><![CDATA[Ajax requests are, generally speaking, used to update the document or meant to send and fetch new data to and from the server. In Ajax heavy apps, you might end up sending the same request on numerous occasions and not always expect the server to respond with the same results.
This can cause problems with caching. [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/ajax/preventing-ajax-request-caching-in-mootools-introducing-requestnocache/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>CiUI Dev on Google Code</title>
		<link>http://www.clientcide.com/best-practices/ciui-dev-on-google-code/</link>
		<comments>http://www.clientcide.com/best-practices/ciui-dev-on-google-code/#comments</comments>
		<pubDate>Fri, 04 Apr 2008 17:59:13 +0000</pubDate>
		<dc:creator>Vladimir Olexa</dc:creator>
				<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[CNET JS Standards]]></category>
		<category><![CDATA[Organizing Code]]></category>
		<category><![CDATA[Widgets]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/uncategorized/ciui-dev-on-google-code/</guid>
		<description><![CDATA[I&#8217;ve created a new development repository on Google Code. I wanted to have a separate development environment for people to work on the library without having to work off of the entire CNET Javascript framework repository. I&#8217;ll be posting CiUI-only releases there before merging them with Clientside&#8217;s repository.
You can also file CiUI specific bugs and [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/ciui-dev-on-google-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mootools 1.0 goes gold, CNET Libraries WikiTorial</title>
		<link>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-10-goes-gold-cnet-libraries-wikitorial/</link>
		<comments>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-10-goes-gold-cnet-libraries-wikitorial/#comments</comments>
		<pubDate>Tue, 30 Jan 2007 20:38:19 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Ajax]]></category>
		<category><![CDATA[CNET JS Standards]]></category>
		<category><![CDATA[Event Scripting]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Manipulating the Dom]]></category>
		<category><![CDATA[MooTools]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[Visual Effects]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/code-snippets/manipulating-the-dom/mootools-10-goes-gold-cnet-libraries-wikitorial/</guid>
		<description><![CDATA[Mootools 1.0 is out. Fancy new site design and docs.
We&#8217;ve already refactored all our code for 1.0, though it is not yet released to the CNET site. We&#8217;re entering into QA now&#8230;
I&#8217;ve also released the second part of my wiki tutorial series, this time giving working examples of all the CNET common code. The CNET [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-10-goes-gold-cnet-libraries-wikitorial/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mootools Primer, CNET Libraries online</title>
		<link>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-primer-cnet-libraries-online/</link>
		<comments>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-primer-cnet-libraries-online/#comments</comments>
		<pubDate>Wed, 22 Nov 2006 20:10:31 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Ajax]]></category>
		<category><![CDATA[CNET JS Standards]]></category>
		<category><![CDATA[Event Scripting]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Manipulating the Dom]]></category>
		<category><![CDATA[MooTools]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[Visual Effects]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/code-snippets/manipulating-the-dom/mootools-primer-cnet-libraries-online/</guid>
		<description><![CDATA[Hi gang,
I&#8217;ve been at work on a mootools primer as a tutorial for those who want to use the library but don&#8217;t know a lot about javascript. It&#8217;s replete with working code examples that you can execute right in the browser and see the result.
I&#8217;m aware that the forthcoming version 1.0 of Mootools contains a [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/manipulating-the-dom/mootools-primer-cnet-libraries-online/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Google&#8217;s Web Toolkit now available for Mac OS X</title>
		<link>http://www.clientcide.com/tools/googles-web-toolkit-now-available-for-mac-os-x/</link>
		<comments>http://www.clientcide.com/tools/googles-web-toolkit-now-available-for-mac-os-x/#comments</comments>
		<pubDate>Mon, 20 Nov 2006 18:56:32 +0000</pubDate>
		<dc:creator>markbult</dc:creator>
				<category><![CDATA['Industry' News]]></category>
		<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/uncategorized/googles-web-toolkit-now-available-for-mac-os-x/</guid>
		<description><![CDATA[Google has released its Google Web Toolkit (GWT) for the Mac. Version 1.2 now works on OS X as well as Linux and Windows.
I haven&#8217;t used it yet, so I can&#8217;t really attest to its capabilities. Basically, though, it allows you to write and debug AJAX web apps in Java and compile them to browser-compliant [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/tools/googles-web-toolkit-now-available-for-mac-os-x/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Back Button Support: Safari and Speed</title>
		<link>http://www.clientcide.com/best-practices/browser-issues/back-button-support-safari-and-speed/</link>
		<comments>http://www.clientcide.com/best-practices/browser-issues/back-button-support-safari-and-speed/#comments</comments>
		<pubDate>Thu, 16 Nov 2006 17:53:52 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Browser Stuff]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/best-practices/browser-issues/back-button-support-safari-and-speed/</guid>
		<description><![CDATA[via Ajaxian:
Daniel Kantor has implemented a Back button solution in Streampad and has shared it with us.
One of the main gripes against AJAX webapps is how they break the back button in a typical browser. There have been a few solutions (notably Brad Neubergâ€™s Really Simple History) but none have got it working in Safari. [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/best-practices/browser-issues/back-button-support-safari-and-speed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mootools Ajax extension for handling errors on CNET</title>
		<link>http://www.clientcide.com/code-snippets/ajax/mootools-ajax-extension-for-handling-errors-on-cnet/</link>
		<comments>http://www.clientcide.com/code-snippets/ajax/mootools-ajax-extension-for-handling-errors-on-cnet/#comments</comments>
		<pubDate>Wed, 27 Sep 2006 18:26:47 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[Ajax]]></category>
		<category><![CDATA[CNET JS Standards]]></category>
		<category><![CDATA[MooTools]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=169</guid>
		<description><![CDATA[CNET always returns response code 200 for it&#8217;s pages, even when they are errors. This presents a problem for any ajax framework you might be using as your ajaxer will always think the page is returning 200, even if it&#8217;s not.
I wrote a quick extention for the Mootools framework as part of my forthcoming release [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/code-snippets/ajax/mootools-ajax-extension-for-handling-errors-on-cnet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mootools</title>
		<link>http://www.clientcide.com/3rd-party-libraries/mootools/</link>
		<comments>http://www.clientcide.com/3rd-party-libraries/mootools/#comments</comments>
		<pubDate>Tue, 19 Sep 2006 18:55:22 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA['Industry' News]]></category>
		<category><![CDATA[3rd Party Libraries]]></category>
		<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Code Snippets]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Manipulating the Dom]]></category>
		<category><![CDATA[MooTools]]></category>
		<category><![CDATA[Reference]]></category>
		<category><![CDATA[Visual Effects]]></category>
		<category><![CDATA[moo.fx]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=157</guid>
		<description><![CDATA[Well crap. 1) I love the mad4milk guys (makers of moo.fx, moo.ajax, moo.dom, prototype.lite). 2) their new framework looks AWESOME. 3) as always, their libraries are SUPER TINY.
But damn, now I have to learn something new, and maybe rewrite a bunch of crap. This is the problem with javascript. Still, when Prototype + Scriptaculous is [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/3rd-party-libraries/mootools/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Surveying open-source AJAX toolkits</title>
		<link>http://www.clientcide.com/3rd-party-libraries/surveying-open-source-ajax-toolkits/</link>
		<comments>http://www.clientcide.com/3rd-party-libraries/surveying-open-source-ajax-toolkits/#comments</comments>
		<pubDate>Thu, 03 Aug 2006 00:44:54 +0000</pubDate>
		<dc:creator>Aaron N.</dc:creator>
				<category><![CDATA[3rd Party Libraries]]></category>
		<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Examples]]></category>
		<category><![CDATA[Prototype]]></category>
		<category><![CDATA[Visual Effects]]></category>

		<guid isPermaLink="false">http://clientside.cnet.com/?p=130</guid>
		<description><![CDATA[One of the aspects of having a lot of action going on around a development space that&#8217;s rather new is that you get a lot of people solving problems just like the ones you&#8217;re having. These people release their work and you can make use of them if you like.
So you go download a few, [...]]]></description>
		<wfw:commentRss>http://www.clientcide.com/3rd-party-libraries/surveying-open-source-ajax-toolkits/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
