<?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>Webmaster-Source &#187; ajax</title>
	<atom:link href="https://www.webmaster-source.com/tag/ajax/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.webmaster-source.com</link>
	<description>Useful Resources For Webmasters</description>
	<lastBuildDate>Thu, 24 Aug 2017 02:01:18 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.42</generator>
	<item>
		<title>JSONView: View JSON Data in Firefox</title>
		<link>https://www.webmaster-source.com/2010/09/24/jsonview-view-json-data-in-firefox/</link>
		<comments>https://www.webmaster-source.com/2010/09/24/jsonview-view-json-data-in-firefox/#comments</comments>
		<pubDate>Fri, 24 Sep 2010 11:47:58 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[json]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/?p=3590</guid>
		<description><![CDATA[JSON is a popular way to format AJAX responses, as it&#8217;s more compact than XML and essentially a JavaScript object, but it can be a real pain to work with due to uncooperative browsers. It&#8217;s easy enough to view XML in a web browser, which is good for testing, but JSON responses cause a download [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>JSON is a popular way to format AJAX responses, as it&#8217;s more compact than XML and essentially a JavaScript object, but it can be a real pain to work with due to uncooperative browsers. It&#8217;s easy enough to view XML in a web browser, which is good for testing, but JSON responses cause a download prompt to open. This makes it harder to verify that an AJAX request is working properly.</p>
<p>Fortunately, a clever developer has built a Firefox extension to solve this problem. <a href="http://benhollis.net/software/jsonview/">JSONView</a> renders a plain-text representation of the JSON object, complete with indentation and color-coding whenever you access a URL that outputs JSON data. For example, the Twitter API. If you click <a href="http://api.twitter.com/1/statuses/user_timeline/redwall_hp.json">this link</a> in Firefox, you will be prompted to download the file. With JSONView installed, you would see output from the following image.</p>
<p><img style=' display: block; margin-right: auto; margin-left: auto;'  class="aligncenter size-full wp-image-3591" title="JSONView JSON Response" src="//www.webmaster-source.com/wp-content/uploads/jsonview-json-response.png" alt="" width="600" height="365" />If you do much JavaScript work, be sure to <a href="http://benhollis.net/software/jsonview/">install JSONView</a>. It will save you some headaches when you have AJAX requests that aren&#8217;t working quite right.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2010/09/24/jsonview-view-json-data-in-firefox/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress JSON API Plugin</title>
		<link>https://www.webmaster-source.com/2010/06/11/wordpress-json-api-plugin/</link>
		<comments>https://www.webmaster-source.com/2010/06/11/wordpress-json-api-plugin/#comments</comments>
		<pubDate>Fri, 11 Jun 2010 11:16:58 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[json]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/?p=3394</guid>
		<description><![CDATA[WordPress provides an RSS feed for just about every part of the website. You can get XML output for anything, from posts to tags to comments. But what if you&#8217;re working with JavaScript? Wouldn&#8217;t it be nice to have a JSON option? That&#8217;s what the JSON API plugin does. Appending ?json=1 to the end of [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>WordPress provides an RSS feed for just about every part of the website. You can get XML output for anything, from posts to tags to comments. But what if you&#8217;re working with JavaScript? Wouldn&#8217;t it be nice to have a JSON option? That&#8217;s what the <a href="http://wordpress.org/extend/plugins/json-api/">JSON API</a> plugin does. Appending <code>?json=1</code> to the end of any WordPress URL will work like the RSS option, but the feed will be formatted as JSON. It can even be used to submit comments, if you invoke the right method.</p>
<blockquote><p>This plugin was created for The Museum of Modern Art, whose weblog <a href="http://moma.org/explore/inside_out">Inside/Out</a> appears within  an existing structure built with Ruby on Rails. Instead of  reimplementing the site templates as a WordPress theme, we opted for a  Rails front-end that displays content served from a WordPress back-end.  JSON API provides the necessary interface for retrieving content and  accepting comment <a href="http://digwp.com/2010/05/wordpress-json-api-plugin/">submissions.</a></p></blockquote>
<p>I like Chris Coyier&#8217;s suggestion of using it in conjunction with the jQuery UI Autocomplete component in order to add a Google Suggest-type feature to your search form.</p>
<p><a href="http://digwp.com/2010/05/wordpress-json-api-plugin/">WordPress JSON API Plugin</a> [Digging into WordPress]</p>
<p><a href="http://wordpress.org/extend/plugins/json-api/other_notes/">JSON API Usage Guide</a> [JSON API]</p>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2010/06/11/wordpress-json-api-plugin/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Loading JavaScript Asynchronously</title>
		<link>https://www.webmaster-source.com/2010/06/07/loading-javascript-asynchronously/</link>
		<comments>https://www.webmaster-source.com/2010/06/07/loading-javascript-asynchronously/#comments</comments>
		<pubDate>Mon, 07 Jun 2010 11:48:50 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[(x)html]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[javascript]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/?p=3383</guid>
		<description><![CDATA[BuySellAds and Google Analytics, in an attempt to make the internet faster, recently changed the code snippets they use for serving ads and tracking visitors, respectively, to be non-blocking and asynchronous. This means that the scripts won&#8217;t hold up the rendering of your pages while they load. If you reload this page, as an example, [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>BuySellAds and Google Analytics, in an attempt to make the internet faster, recently changed the code snippets they use for serving ads and tracking visitors, respectively, to be <em>non-blocking</em> and <em>asynchronous</em>. This means that the scripts won&#8217;t hold up the rendering of your pages while they load. If you reload this page, as an example, the ads to the right may actually appear after the rest of the page has finished loading. It gives the appearance of being a lot faster.</p>
<p>How can you load your own scripts asynchronously? Here&#8217;s an example I put together after dissecting Googles&#8217; and BuySellAds&#8217; scripts:</p>
<pre class="brush: xml; title: ; notranslate">
&lt;script id=&quot;myscript&quot; type=&quot;text/javascript&quot;&gt;

(function() {
 var myscript = document.createElement('script');
 myscript.type = 'text/javascript';
 myscript.src = ('http://example.org/myscript.js');
 var s = document.getElementById('myscript');
 s.parentNode.insertBefore(myscript, s);
})();

&lt;/script&gt;
</pre>
<p>What it does is it dynamically assembles and writes out a <code>&lt;script type="text/javascript" src="..." /&gt;</code> DOM element, placing it just before the loader script. You could alter the <code>insertBefore</code> part to append loaded script to the <code>&lt;head&gt;</code> element if you&#8217;re so inclined.</p>
<p>You can read further on this technique from these sources:</p>
<ul>
<li><a href="http://www.artzstudio.com/2008/07/beating-blocking-javascript-asynchronous-js/">Beating Blocking JavaScript: Asynchronous JS</a></li>
<li><a href="http://blog.buysellads.com/2010/02/new-feature-non-blocking-asynchronous-ad-code/">New Feature: Non-blocking, Asynchronous Ad Code</a></li>
<li><a href="http://code.google.com/apis/analytics/docs/tracking/asyncTracking.html">Tracking Sites with the Asynchronous Snippet</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2010/06/07/loading-javascript-asynchronously/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Twitter List-Powered &#8220;Fan Page&#8221; Widget</title>
		<link>https://www.webmaster-source.com/2010/01/15/twitter-list-powered-fan-page-widget/</link>
		<comments>https://www.webmaster-source.com/2010/01/15/twitter-list-powered-fan-page-widget/#comments</comments>
		<pubDate>Fri, 15 Jan 2010 11:52:10 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[Social Media]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[widgets]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/?p=2928</guid>
		<description><![CDATA[There&#8217;s a really neat post over at Tutorialzine on how to build A Twitter List Powered Fan Page. It&#8217;s a little widget, that would go in your sidebar or some similar place, where it would display the Twitter avatars of anyone who wanted to click a button to add themselves to a Twitter List (along [&#8230;]]]></description>
				<content:encoded><![CDATA[<p><a href="http://demo.tutorialzine.com/2009/11/twitter-list-ajax-fanpage/demo.html"><img style=' float: right; padding: 4px; margin: 0 0 2px 7px;'  class="alignright size-full wp-image-2929 imgborder" title="Twitter List Powered Fan Page" src="//www.webmaster-source.com/wp-content/uploads/twitter-list-powered-fan-page.jpg" alt="" width="135" height="213" /></a>There&#8217;s a really neat post over at Tutorialzine on how to build <a href="http://tutorialzine.com/2009/11/twitter-list-ajax-fanpage/">A Twitter List Powered Fan Page</a>.</p>
<p>It&#8217;s a little widget, that would go in your sidebar or some similar place, where it would display the Twitter avatars of anyone who wanted to click a button to add themselves to a Twitter List (along with an overall count of the &#8220;fans&#8221;).</p>
<p>It seems like a neat idea, though you have to do a bit of PHP and JavaScript work to get it up an running. (It would be nice to see a variation made as a WordPress plugin&#8230;)</p>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2010/01/15/twitter-list-powered-fan-page-widget/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GetGravatar jQuery Plugin</title>
		<link>https://www.webmaster-source.com/2009/09/03/getgravatar-jquery-plugin/</link>
		<comments>https://www.webmaster-source.com/2009/09/03/getgravatar-jquery-plugin/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 11:46:12 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[Gravatar]]></category>
		<category><![CDATA[jquery]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/?p=2520</guid>
		<description><![CDATA[GetGravatar is a jQuery plugin that is a perfect touch for blog comment forms. It monitors an email address form input, and makes an AJAX request to load a Gravatar. (See a demo.) This would enable you to show a user&#8217;s Gravatar next to the comment form immediately after they input their email. Get Gravatar [&#8230;]]]></description>
				<content:encoded><![CDATA[<p><a href="http://pixelmatrixdesign.com/weblog/comments/announcing_get_gravatar/">GetGravatar</a> is a jQuery plugin that is a perfect touch for blog comment forms. It monitors an email address form input, and makes an AJAX request to load a Gravatar. (See a <a href="http://pixelmatrixdesign.com/playground/getgravatar/">demo</a>.) This would enable you to show a user&#8217;s Gravatar next to the comment form immediately after they input their email.</p>
<blockquote><p>Get Gravatar is meant to be used with a text input. As the text changes in the input, it pings the Gravatar service to fetch the userâ€™s avatar. Due to Gravatarâ€™s restrictions, Gravatars must be retrieved with an MD5 hash of the userâ€™s email. Since Javascript doesnâ€™t have a built-in way to fetch an MD5 hash, this plugin has a PHP counterpart.</p></blockquote>
<p>Obviously there are more creative uses for this, but either way it&#8217;s a nifty script.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2009/09/03/getgravatar-jquery-plugin/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google AJAX Libraries API</title>
		<link>https://www.webmaster-source.com/2009/01/21/google-ajax-libraries-api/</link>
		<comments>https://www.webmaster-source.com/2009/01/21/google-ajax-libraries-api/#comments</comments>
		<pubDate>Wed, 21 Jan 2009 12:11:15 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[jquery]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/?p=1747</guid>
		<description><![CDATA[Do you use a JavaScript library â€” such as jQuery, Prototype, or MooTools â€” on one (or more) of your websites? That probably adds a good 18-120 kilobytes to your pages&#8217; total size, adding more time to users&#8217; download time. Now, how many websites use that same framework? How many websites make use of jQuery, [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Do you use a JavaScript library â€” such as <a href="http://jquery.com">jQuery</a>, <a href="http://www.prototypejs.org/">Prototype</a>, or <a href="http://www.mootools.net/">MooTools</a> â€” on one (or more) of your websites? That probably adds a good 18-120 kilobytes to your pages&#8217; total size, adding more time to users&#8217; download time.</p>
<p>Now, how many websites use that same framework? How many websites make use of jQuery, or example? A lot. That means any given user could be downloading the JavaScript files multiple times in a day, as different sites require it. What a waste of time and bandwidth.</p>
<p><img style=' float: right; padding: 4px; margin: 0 0 2px 7px;'  class="alignright" title="Google AJAX Library API" src="http://i41.tinypic.com/10ghbmp.jpg" alt="" width="160" height="100" />Google has an interesting solution. They host <a href="http://code.google.com/apis/ajaxlibs/">multiple versions of several major JavaScript libraries</a> on their servers for web developers to take advantage of. This offers several advantages. Their servers are quick and have wide pipes allowing for very fast downloads, for one. The real benefit is caching.</p>
<p>If a user visits several sites that reference jQuery (or another library) from Google, their browser caches the file and will only load it once, reusing the cached file on the other sites when they are loaded. This is because you&#8217;re referencing a file from <em>ajax.googleapis.com</em> instead of your own domain, and if multiple sites reference it, the browser remembers it already downloaded the file and uses the local copy.<span id="more-1747"></span></p>
<p>The libraries available at the present are:</p>
<ul>
<li>jQuery</li>
<li>jQuery UI</li>
<li>Prototype</li>
<li>script.aculo.us</li>
<li>MooTools</li>
<li>Dojo</li>
<li>SWFObject</li>
<li>Yahoo UI Library</li>
</ul>
<p>To reference one, you simply call the JavaScript file as you normally would, but put the <a href="http://code.google.com/apis/ajaxlibs/documentation/index.html">URL on Google&#8217;s servers</a> instead of your own. For example, to load jQuery 1.3.0 you would use the following:</p>
<p><code>&lt;script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.0/jquery.min.js"&gt;&lt;/script&gt;</code></p>
<p>Simple, and a good way to cut down on page load time. The only downside is, if Google were to have problems with the servers that host the scripts, we would be looking at a web-wide lack of scripts that may be critical to the operation of some sites. Google is known to be fairly reliable, but you never know, it&#8217;s always possible that the supposedly impossible could happen. Then we would have a problem like the <a href="http://www.centernetworks.com/amazon-s3-down-july-2008">Amazon S3 outage last year</a>, where scores of sites were affected. (Twitter&#8217;s avatars went AWOL, SmugMug had photos not showing, some podcasts weren&#8217;t downloadable, etc..)</p>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2009/01/21/google-ajax-libraries-api/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>AJAX, Disambiguation</title>
		<link>https://www.webmaster-source.com/2008/10/13/ajax-disambiguation/</link>
		<comments>https://www.webmaster-source.com/2008/10/13/ajax-disambiguation/#comments</comments>
		<pubDate>Mon, 13 Oct 2008 10:09:45 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[DHTML]]></category>
		<category><![CDATA[javascript]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/?p=912</guid>
		<description><![CDATA[&#8220;AJAX,&#8221; which stands for &#8220;Asynchronous Javascript and XML&#8221; has sadly been being used as a buzzword lately, referring to Javascript/DHTML tricks rather than it&#8217;s &#8220;real&#8221; meaning. AJAX is the use of the XMLHttpRequest object in JavaScript to load new content from a server into a page, without reloading the page. A good example of this [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>&#8220;AJAX,&#8221; which stands for &#8220;Asynchronous Javascript and XML&#8221; has sadly been being used as a buzzword lately, referring to Javascript/DHTML tricks rather than it&#8217;s &#8220;real&#8221; meaning.</p>
<p>AJAX is the use of the XMLHttpRequest object in JavaScript to load new content from a server into a page, without reloading the page. A good example of this is <a href="http://twitter.com">Twitter</a>. Type your new message into the box, press the button, and your message is sent to the server (and a response is sent back) without the page being reloaded. This is AJAX.</p>
<p>What AJAX <em>isn&#8217;t</em>, but people keep referring to as AJAX, is dynamic Javascript tricks such as <a href="http://scriptaculous.com">Script.aculo.us</a> effects.</p>
<p>Please use the term &#8220;AJAX&#8221; to refer to asynchronous HTTP requests, and not any old bit of JavaScript. We already have a term for that, it&#8217;s &#8220;DHTML,&#8221;Â  or &#8220;Dynamic HTML.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2008/10/13/ajax-disambiguation/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>FaceBox: Facebook-Style JavaScript Overlays</title>
		<link>https://www.webmaster-source.com/2008/03/31/facebox-facebook-style-javascript-overlays/</link>
		<comments>https://www.webmaster-source.com/2008/03/31/facebox-facebook-style-javascript-overlays/#comments</comments>
		<pubDate>Mon, 31 Mar 2008 12:31:51 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[Software & Scripts]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[jquery]]></category>
		<category><![CDATA[lightbox]]></category>
		<category><![CDATA[Overlay]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/?p=477</guid>
		<description><![CDATA[Lightbox-type DIV overlays have a multitude of uses. If you&#8217;re building a web app, or if you are just looking for a way to declutter your blog, you can just sweep elements under the proverbial rug until they&#8217;re needed, and then call them back in a &#8220;almost-window.&#8221; FaceBox, is yet another way of implementing this [&#8230;]]]></description>
				<content:encoded><![CDATA[<p><img src="http://i28.tinypic.com/28kpt9x.jpg" alt="FaceBox Dialog" hspace="5" vspace="5" align="right" /><a href="http://www.huddletogether.com/projects/lightbox2/">Lightbox</a>-type DIV overlays have a multitude of uses. If you&#8217;re building a web app, or if you are just looking for a way to declutter your blog, you can just sweep elements under the proverbial rug until they&#8217;re needed, and then call them back in a &#8220;almost-window.&#8221;</p>
<p><a href="http://famspam.com/facebox/">FaceBox</a>, is yet another way of implementing this functionality, but styled in a similar manner to FaceBook&#8217;s pop-up boxes.</p>
<p>FaceBox can display DIVs, images, AJAX-loaded pages, or you can just write content in dynamically via JavaScript. It&#8217;s fairly easy to implement the script, though it took me a little bit of tweaking to get all of the images to display correctly (I just had to change a few paths throughout the code).</p>
<p>The JavaScript file is just 6KB, and the 1KB worth of CSS can easily be pasted into your existing stylesheet, or referenced separately. There are also a few assorted images that are required, though they&#8217;re mainly under 1K. Also note that FaceBox requires jQuery to function, so you may not want it if you&#8217;re a Prototype aficionado.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2008/03/31/facebox-facebook-style-javascript-overlays/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AJAX Whois</title>
		<link>https://www.webmaster-source.com/2008/03/30/ajax-whois/</link>
		<comments>https://www.webmaster-source.com/2008/03/30/ajax-whois/#comments</comments>
		<pubDate>Sun, 30 Mar 2008 13:14:10 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[Domains]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[whois]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/?p=476</guid>
		<description><![CDATA[I recently stumbled across AJAX Whois, which may have become my new favorite way to find domains and check WhoIs info. It&#8217;s fast, and it&#8217;s easy to use. I&#8217;m serious when I say AJAX Whois is fast. Start typing in the form, and the web app searches as you type. By the time you&#8217;ve finished [&#8230;]]]></description>
				<content:encoded><![CDATA[<p><img src="http://i25.tinypic.com/2qxvodt.jpg" alt="AJAX Whois" hspace="5" vspace="5" width="270" height="159" align="right" />I recently stumbled across <a href="http://ajaxwhois.com/">AJAX Whois</a>, which may have become my new favorite way to find domains and check WhoIs info. It&#8217;s fast, and it&#8217;s easy to use.</p>
<p>I&#8217;m serious when I say AJAX Whois is fast. Start typing in the form, and the web app searches as you type. By the time you&#8217;ve finished typing in a domain, the results are already there.</p>
<p>There are a couple of small features that really make the site easier to use. Number one is the favorites feature. If you find a domain that you want to remember while you&#8217;re searching other ones, you can just click the favorite button and it will be added to a space in the sidebar for easy access. The other feature is even simpler, yet you would really miss it if it wasn&#8217;t there; You don&#8217;t have to enter a TLD when searching. Many whois services require that you enter a TLD, even if you want to see results for multiple TLDs. Luckily AJAX Whois doesn&#8217;t follow that trend.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2008/03/30/ajax-whois/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>When Should You Use AJAX?</title>
		<link>https://www.webmaster-source.com/2008/01/09/when-should-you-use-ajax/</link>
		<comments>https://www.webmaster-source.com/2008/01/09/when-should-you-use-ajax/#comments</comments>
		<pubDate>Wed, 09 Jan 2008 12:47:24 +0000</pubDate>
		<dc:creator><![CDATA[Matt]]></dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://www.webmaster-source.com/2008/01/09/when-should-you-use-ajax/</guid>
		<description><![CDATA[AJAX, or Asynchronous JavaScript and XML, was probably the most-hyped web programming technique in the last two years. It&#8217;s no surprise, as it enables you to do a lot that couldn&#8217;t have been done just a few years ago. AJAX is being used in more and more places, often when it doesn&#8217;t need to be&#8230;and [&#8230;]]]></description>
				<content:encoded><![CDATA[<p><a href="http://en.wikipedia.org/wiki/Ajax_%28programming%29">AJAX</a>, or Asynchronous JavaScript and XML, was probably the most-hyped web programming technique in the last two years. It&#8217;s no surprise, as it enables you to do a lot that couldn&#8217;t have been done just a few years ago.</p>
<p>AJAX is being used in more and more places, often when it doesn&#8217;t need to be&#8230;and when it shouldn&#8217;t. <strong>With all the talk about how you can use AJAX for everything, the real question is when <em>should</em> you.</strong></p>
<p>You should use AJAX in places where it will improve the user experience. One example is with polls. Why should a full pageload be required just to vote in a poll (or view the results)? That&#8217;s a waste of your users&#8217; time, and a waste of your server resources.</p>
<p><strong>Do not use AJAX for loading your main content</strong>, though. It&#8217;s not a good idea. I&#8217;ve seen a few sites that have tried it, and it doesn&#8217;t work that well. You have to come up with extra solutions for search engines, because they can&#8217;t understand your JavaScript trickery (you thought the dreaded &#8220;text-only version&#8221; link only applied to Flash sites? ). You also cause problems for people using some browsers (Safari, IE5, etc).</p>
<p>Basically, you want to use AJAX for things where an extra pageload would be irritate the heck out of everyone. Suppose you have a star-rating system, like on Netflix. Wouldn&#8217;t it be horrible if you had to sit through a page refresh every time you rated a movie? Use your own judgment.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.webmaster-source.com/2008/01/09/when-should-you-use-ajax/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/


Served from: www.webmaster-source.com @ 2026-04-05 02:54:28 by W3 Total Cache
-->