<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Google Search: Next-generation Architecture</title>
	<atom:link href="http://wir-sprechen-online.com/2009/08/11/google-search-next-generation-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://wir-sprechen-online.com/2009/08/11/google-search-next-generation-architecture/</link>
	<description></description>
	<lastBuildDate>Sun, 03 Jun 2012 05:00:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Google Rolls Out Caffeine &#171; Wir sprechen Online.</title>
		<link>http://wir-sprechen-online.com/2009/08/11/google-search-next-generation-architecture/#comment-13170</link>
		<dc:creator><![CDATA[Google Rolls Out Caffeine &#171; Wir sprechen Online.]]></dc:creator>
		<pubDate>Wed, 09 Jun 2010 04:57:22 +0000</pubDate>
		<guid isPermaLink="false">http://wir-sprechen-online.com/?p=7171#comment-13170</guid>
		<description><![CDATA[[...] Google announced the completion and global roll out of its new web indexing system Caffeine; http://j.mp/doUJjN  [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Google announced the completion and global roll out of its new web indexing system Caffeine; <a href="http://j.mp/doUJjN" rel="nofollow">http://j.mp/doUJjN</a>  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google vs. Google Caffeine « Wir sprechen Online.</title>
		<link>http://wir-sprechen-online.com/2009/08/11/google-search-next-generation-architecture/#comment-3291</link>
		<dc:creator><![CDATA[Google vs. Google Caffeine « Wir sprechen Online.]]></dc:creator>
		<pubDate>Wed, 12 Aug 2009 22:01:20 +0000</pubDate>
		<guid isPermaLink="false">http://wir-sprechen-online.com/?p=7171#comment-3291</guid>
		<description><![CDATA[[...] Compare Google results with Google Caffeine results side by side at Facesaerch; http://bit.ly/qwskm [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Compare Google results with Google Caffeine results side by side at Facesaerch; <a href="http://bit.ly/qwskm" rel="nofollow">http://bit.ly/qwskm</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gerrit Eicker</title>
		<link>http://wir-sprechen-online.com/2009/08/11/google-search-next-generation-architecture/#comment-3278</link>
		<dc:creator><![CDATA[Gerrit Eicker]]></dc:creator>
		<pubDate>Tue, 11 Aug 2009 06:00:04 +0000</pubDate>
		<guid isPermaLink="false">http://wir-sprechen-online.com/?p=7171#comment-3278</guid>
		<description><![CDATA[&lt;a href=&quot;http://googlewebmastercentral.blogspot.com/2009/08/help-test-some-next-generation.html&quot; rel=&quot;nofollow&quot;&gt;Google&lt;/a&gt;: &quot;&lt;strong&gt;For the last several months, a large team of Googlers has been working on a secret project: a next-generation architecture for Google&#039;s web search.&lt;/strong&gt; It&#039;s the first step in a process that will let us push the envelope on size, indexing speed, accuracy, comprehensiveness and other dimensions. &lt;strong&gt;The new infrastructure sits &#039;under the hood&#039; of Google&#039;s search engine&lt;/strong&gt;, which means that most users won&#039;t notice a difference in search results. But web developers and power searchers might notice a few differences, so we&#039;re opening up a web developer preview to collect feedback.&quot;

&lt;a href=&quot;http://www.techcrunch.com/2009/08/10/caffeine-its-google-on-red-bull-or-something/&quot; rel=&quot;nofollow&quot;&gt;TC&lt;/a&gt;: &quot;&lt;strong&gt;Search Engines are like sharks: If they stop moving, they die.&lt;/strong&gt; - Google, as the king of search engines, obviously has been doing that constantly throughout the years. Some of the changes are noticeable, but most are subtle tweaks on a rolling basis. - But today, the company has begun testing a new engine for its search product that’s a big enough change that it felt compelled to let the world know about it. &lt;strong&gt;Codenamed &#039;Caffeine&#039;, it promises to &#039;push the envelope on size, indexing speed, accuracy, comprehensiveness and other dimensions.&#039;&lt;/strong&gt;”

&lt;a href=&quot;http://www.mattcutts.com/blog/caffeine-update/&quot; rel=&quot;nofollow&quot;&gt;Cutts&lt;/a&gt;: &quot;Google recently opened up a preview of our new Caffeine update, and I wanted to give &lt;strong&gt;a little more background on this change&lt;/strong&gt;.&quot;

&lt;a href=&quot;http://www.readwriteweb.com/archives/caffeine_google_tests_new_search_infrastructure.php&quot; rel=&quot;nofollow&quot;&gt;RWW&lt;/a&gt;: &quot;&lt;strong&gt;From a consumer standpoint, Caffeine is identical to regular Google search&lt;/strong&gt; save for shaving off a few precious half seconds. But for search engine marketers, the new indexing system adds another hurdle to their jobs. While it&#039;s likely that Google will have at least a month head start in outrunning them, in the past savvy keyword specialists have always managed to make their mark. - &lt;strong&gt;To help improve Caffeine, search in the sandbox and click the &#039;Dissatisfied? Help us improve&#039; link to offer feedback.&lt;/strong&gt;&quot;]]></description>
		<content:encoded><![CDATA[<p><a href="http://googlewebmastercentral.blogspot.com/2009/08/help-test-some-next-generation.html" rel="nofollow">Google</a>: &#8220;<strong>For the last several months, a large team of Googlers has been working on a secret project: a next-generation architecture for Google&#8217;s web search.</strong> It&#8217;s the first step in a process that will let us push the envelope on size, indexing speed, accuracy, comprehensiveness and other dimensions. <strong>The new infrastructure sits &#8216;under the hood&#8217; of Google&#8217;s search engine</strong>, which means that most users won&#8217;t notice a difference in search results. But web developers and power searchers might notice a few differences, so we&#8217;re opening up a web developer preview to collect feedback.&#8221;</p>
<p><a href="http://www.techcrunch.com/2009/08/10/caffeine-its-google-on-red-bull-or-something/" rel="nofollow">TC</a>: &#8220;<strong>Search Engines are like sharks: If they stop moving, they die.</strong> &#8211; Google, as the king of search engines, obviously has been doing that constantly throughout the years. Some of the changes are noticeable, but most are subtle tweaks on a rolling basis. &#8211; But today, the company has begun testing a new engine for its search product that’s a big enough change that it felt compelled to let the world know about it. <strong>Codenamed &#8216;Caffeine&#8217;, it promises to &#8216;push the envelope on size, indexing speed, accuracy, comprehensiveness and other dimensions.&#8217;</strong>”</p>
<p><a href="http://www.mattcutts.com/blog/caffeine-update/" rel="nofollow">Cutts</a>: &#8220;Google recently opened up a preview of our new Caffeine update, and I wanted to give <strong>a little more background on this change</strong>.&#8221;</p>
<p><a href="http://www.readwriteweb.com/archives/caffeine_google_tests_new_search_infrastructure.php" rel="nofollow">RWW</a>: &#8220;<strong>From a consumer standpoint, Caffeine is identical to regular Google search</strong> save for shaving off a few precious half seconds. But for search engine marketers, the new indexing system adds another hurdle to their jobs. While it&#8217;s likely that Google will have at least a month head start in outrunning them, in the past savvy keyword specialists have always managed to make their mark. &#8211; <strong>To help improve Caffeine, search in the sandbox and click the &#8216;Dissatisfied? Help us improve&#8217; link to offer feedback.</strong>&#8220;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

