<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Old wine in a new bottle</title>
	<atom:link href="http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle/feed" rel="self" type="application/rss+xml" />
	<link>http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle</link>
	<description>Random musings of a Southern geek</description>
	<pubDate>Wed, 08 Oct 2008 02:36:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Reign</title>
		<link>http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-159229</link>
		<dc:creator>Reign</dc:creator>
		<pubDate>Thu, 27 Sep 2007 02:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-159229</guid>
		<description>I'm new to this AJAX thing and slowly learning everything about it, and I'm glad that you guys, a discussion like this are a great help to me. Thank you.</description>
		<content:encoded><![CDATA[<p>I&#8217;m new to this <acronym title='Asynchronous Javascript and XML'><span class='caps'>AJAX</span></acronym> thing and slowly learning everything about it, and I&#8217;m glad that you guys, a discussion like this are a great help to me. Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Iwo</title>
		<link>http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-157017</link>
		<dc:creator>Iwo</dc:creator>
		<pubDate>Thu, 01 Mar 2007 16:52:17 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-157017</guid>
		<description>Good point, its been around for some time but now the web environment is able to support remote scripting much better.</description>
		<content:encoded><![CDATA[<p>Good point, its been around for some time but now the web environment is able to support remote scripting much better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dougal</title>
		<link>http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-19887</link>
		<dc:creator>Dougal</dc:creator>
		<pubDate>Tue, 24 May 2005 13:08:07 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-19887</guid>
		<description>Ajax's affect on search engine indexing will depend entirely on how you use it. If your pages are designed to still function normally without Ajax, then it shouldn't affect the indexing. If you design your pages such that they can only be used with Javascript enabled, then it could prevent search engines from seeing some of your content (depending on exactly what you're using Ajax &lt;em&gt;for&lt;/em&gt;.</description>
		<content:encoded><![CDATA[<p>Ajax&#8217;s affect on search engine indexing will depend entirely on how you use it. If your pages are designed to still function normally without Ajax, then it shouldn&#8217;t affect the indexing. If you design your pages such that they can only be used with Javascript enabled, then it could prevent search engines from seeing some of your content (depending on exactly what you&#8217;re using Ajax <em>for</em>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bald Eagle</title>
		<link>http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-19847</link>
		<dc:creator>Bald Eagle</dc:creator>
		<pubDate>Mon, 23 May 2005 23:12:39 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-19847</guid>
		<description>The â€œright place, right timeâ€ factor is were itâ€™s at I think. The same holds true for cascading style sheets. Now you can design/develop entirely in CCS and forget about tables. In IE that is. Unfortunately, Firefox is gaining market share, but the current version has its flaws when it comes to supporting CSS.

I am wondering: how does using AJAX influence a web pageâ€™s ability to get indexed by search engines?</description>
		<content:encoded><![CDATA[<p>The â€œright place, right timeâ€ factor is were itâ€™s at I think. The same holds true for cascading style sheets. Now you can design/develop entirely in CCS and forget about tables. In <acronym title='Internet Explorer'><span class='caps'>IE</span></acronym> that is. Unfortunately, Firefox is gaining market share, but the current version has its flaws when it comes to supporting <acronym title='Cascading Style Sheets'><span class='caps'>CSS</span></acronym>.</p>
<p>I am wondering: how does using <acronym title='Asynchronous Javascript and XML'><span class='caps'>AJAX</span></acronym> influence a web pageâ€™s ability to get indexed by search engines?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jbot</title>
		<link>http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-19680</link>
		<dc:creator>jbot</dc:creator>
		<pubDate>Thu, 19 May 2005 15:46:15 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-19680</guid>
		<description>@Kevin Clary:

Let's face it, Adaptive Path are just bandwaggoning. They hope to get more business, sell more seminars, from this, because they hope by attaching a new name to an old technology they'll get all the plaudits and more revenue. It's a con. They've invented nothing, but hike up their own plublicity.</description>
		<content:encoded><![CDATA[<p>@Kevin Clary:</p>
<p>Let&#8217;s face it, Adaptive Path are just bandwaggoning. They hope to get more business, sell more seminars, from this, because they hope by attaching a new name to an old technology they&#8217;ll get all the plaudits and more revenue. It&#8217;s a con. They&#8217;ve invented nothing, but hike up their own plublicity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Clary</title>
		<link>http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-10751</link>
		<dc:creator>Kevin Clary</dc:creator>
		<pubDate>Fri, 25 Mar 2005 18:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-10751</guid>
		<description>Why is Ajax hot now?  One word, Google.</description>
		<content:encoded><![CDATA[<p>Why is Ajax hot now?  One word, Google.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dougal</title>
		<link>http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-10737</link>
		<dc:creator>Dougal</dc:creator>
		<pubDate>Thu, 24 Mar 2005 20:56:16 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-10737</guid>
		<description>Bill S.: I don't see anything in the original article that states in black-and-white that there is a real distinction between Ajax and Remote Scripting. It &lt;em&gt;does&lt;/em&gt; specifically mention XMLHttpRequest as a key component, though. So, technically, you could exclude non-XHR methods from the Ajax umbrella, if you want to be pedantic.

However, I think you'll find that however specific some people might want to be, the term "Ajax" is going to encompass a more generic range, as I've outlined here. At a high level, there is little difference between using IFRAME-based communication or XHR. It's an implementation detail. Developers are going to freely attach the Ajax moniker to these similar techniques just as a matter of convenience.

It's kind of like the whole "hacker vs cracker" debate. Many people spend a lot of energy trying to educate the world on the distinction. But the world doesn't give a flip. Even I've given up on that one. I use the word "hacker" for both cases, and let context define the distinction, and when necessary, I explain the difference to my audience.
</description>
		<content:encoded><![CDATA[<p>Bill S.: I don&#8217;t see anything in the original article that states in black-and-white that there is a real distinction between Ajax and Remote Scripting. It <em>does</em> specifically mention XMLHttpRequest as a key component, though. So, technically, you could exclude non-XHR methods from the Ajax umbrella, if you want to be pedantic.</p>
<p>However, I think you&#8217;ll find that however specific some people might want to be, the term &#8220;Ajax&#8221; is going to encompass a more generic range, as I&#8217;ve outlined here. At a high level, there is little difference between using IFRAME-based communication or XHR. It&#8217;s an implementation detail. Developers are going to freely attach the Ajax moniker to these similar techniques just as a matter of convenience.</p>
<p>It&#8217;s kind of like the whole &#8220;hacker vs cracker&#8221; debate. Many people spend a lot of energy trying to educate the world on the distinction. But the world doesn&#8217;t give a flip. Even I&#8217;ve given up on that one. I use the word &#8220;hacker&#8221; for both cases, and let context define the distinction, and when necessary, I explain the difference to my audience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronaldo</title>
		<link>http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-10736</link>
		<dc:creator>Ronaldo</dc:creator>
		<pubDate>Thu, 24 Mar 2005 20:10:27 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-10736</guid>
		<description>I coming to agree with the "right time, right place" theory, adding also a "right name" to it. Like Brent, I've been using it for years already and was surprised to see it get so much press recently.

What worries about the whole thing is how it will affect accessibility and the proper use of standards. That's a lot harder to do in an Ajax context and people will tend to worry less about it since, in some cases, may mean double the work.</description>
		<content:encoded><![CDATA[<p>I coming to agree with the &#8220;right time, right place&#8221; theory, adding also a &#8220;right name&#8221; to it. Like Brent, I&#8217;ve been using it for years already and was surprised to see it get so much press recently.</p>
<p>What worries about the whole thing is how it will affect accessibility and the proper use of standards. That&#8217;s a lot harder to do in an Ajax context and people will tend to worry less about it since, in some cases, may mean double the work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill S.</title>
		<link>http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-10735</link>
		<dc:creator>Bill S.</dc:creator>
		<pubDate>Thu, 24 Mar 2005 20:08:05 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-10735</guid>
		<description>One correction. You say that Ajax is Remote Scripting OR XMLHttpRequest. The article that coined the name states that is not either OR but it is XMLHttpRequest and NOT remote scripting. There is a big difference. Remote scripting requests through HTTPRequest for a standard HTML GET and then usually copies the results to some innerHTML elsewhere on the page. With XMLHttpRequest you get data back and manipulate it on the client. The data could be XML or Javascript or HTML but it is extremely fast. 

We have been using remote scripting for a few years. Once converting over to XMLHttpRequest we are seeing 10-50 time speed improvements.

The key is the concept of micro-requests and not page requests. Sure some people have done it before, but classifying and naming an approach is a key to wide spread adoption.

Adoption of this opens up the door for fine-grained events performed Asynchronously.


See
http://www.adaptivepath.com/publications/essays/archives/000385.php

And
http://jpspan.sourceforge.net/wiki/doku.php?id=javascript:xmlhttprequest

</description>
		<content:encoded><![CDATA[<p>One correction. You say that Ajax is Remote Scripting OR XMLHttpRequest. The article that coined the name states that is not either OR but it is XMLHttpRequest and NOT remote scripting. There is a big difference. Remote scripting requests through HTTPRequest for a standard <acronym title='HyperText Markup Language'><span class='caps'>HTML</span></acronym> GET and then usually copies the results to some innerHTML elsewhere on the page. With XMLHttpRequest you get data back and manipulate it on the client. The data could be <acronym title='eXtensible Markup Language'><span class='caps'>XML</span></acronym> or Javascript or <acronym title='HyperText Markup Language'><span class='caps'>HTML</span></acronym> but it is extremely fast. </p>
<p>We have been using remote scripting for a few years. Once converting over to XMLHttpRequest we are seeing 10-50 time speed improvements.</p>
<p>The key is the concept of micro-requests and not page requests. Sure some people have done it before, but classifying and naming an approach is a key to wide spread adoption.</p>
<p>Adoption of this opens up the door for fine-grained events performed Asynchronously.</p>
<p>See<br />
<a href="http://www.adaptivepath.com/publications/essays/archives/000385.php" >http://www.adaptivepath.com/publications/essays/archives/000385.php</a></p>
<p>And<br />
<a href="http://jpspan.sourceforge.net/wiki/doku.php?id=javascript:xmlhttprequest" >http://jpspan.sourceforge.net/wiki/doku.php?id=javascript:xmlhttprequest</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike P.</title>
		<link>http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-10734</link>
		<dc:creator>Mike P.</dc:creator>
		<pubDate>Thu, 24 Mar 2005 19:48:49 +0000</pubDate>
		<guid isPermaLink="false">http://dougal.gunters.org/blog/2005/03/24/old-wine-in-a-new-bottle#comment-10734</guid>
		<description>I have a &lt;a href="http://www.fiftyfoureleven.com/weblog/marketing/ajax-from-a-different-pov" rel="nofollow"&gt;theory why it happened&lt;/a&gt;, or maybe that's just a name for it ;-)

Gotta say your name would'a been more catchy...</description>
		<content:encoded><![CDATA[<p>I have a <a href="http://www.fiftyfoureleven.com/weblog/marketing/ajax-from-a-different-pov" >theory why it happened</a>, or maybe that&#8217;s just a name for it <img src='http://dougal.gunters.org/wordpress/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Gotta say your name would&#8217;a been more catchy&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
