<?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/"
		>
<channel>
	<title>Comments on: Google announces new AJAX Feed API</title>
	<atom:link href="http://ajaxian.com/archives/google-announces-new-ajax-feed-api/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 17 May 2012 07:43:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: vidaldewit</title>
		<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api/comment-page-1#comment-262840</link>
		<dc:creator>vidaldewit</dc:creator>
		<pubDate>Tue, 15 Apr 2008 10:21:10 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2321#comment-262840</guid>
		<description>Hi Everybody, I&#039;ve just finished my new job search engine based on Google AJAX Feed API. 
JobGeni - The Realtime Job Aggregator http://www.jobgeni.com pulls the data from several major job sites like indeed, simplyhired, yahoo hotjobs, monster and jobster.</description>
		<content:encoded><![CDATA[<p>Hi Everybody, I&#8217;ve just finished my new job search engine based on Google AJAX Feed API.<br />
JobGeni &#8211; The Realtime Job Aggregator <a href="http://www.jobgeni.com" rel="nofollow">http://www.jobgeni.com</a> pulls the data from several major job sites like indeed, simplyhired, yahoo hotjobs, monster and jobster.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adnan Siddiqi</title>
		<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api/comment-page-1#comment-249653</link>
		<dc:creator>Adnan Siddiqi</dc:creator>
		<pubDate>Fri, 20 Apr 2007 19:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2321#comment-249653</guid>
		<description>no comparion between Feed API and Pipes.</description>
		<content:encoded><![CDATA[<p>no comparion between Feed API and Pipes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: henry turner</title>
		<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api/comment-page-1#comment-249647</link>
		<dc:creator>henry turner</dc:creator>
		<pubDate>Fri, 20 Apr 2007 16:10:06 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2321#comment-249647</guid>
		<description>Does this technology just use document.write and some dynamic script insertions or something? It can&#039;t be Ajax if the proxy is on google&#039;s domain and my page is on my domain.</description>
		<content:encoded><![CDATA[<p>Does this technology just use document.write and some dynamic script insertions or something? It can&#8217;t be Ajax if the proxy is on google&#8217;s domain and my page is on my domain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Burton</title>
		<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api/comment-page-1#comment-249622</link>
		<dc:creator>Kevin Burton</dc:creator>
		<pubDate>Fri, 20 Apr 2007 04:35:29 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2321#comment-249622</guid>
		<description>This has actually been available for a while.  It just wasn&#039;t really obvious.

We have a lot of people using Spinn3r for similar purposes and solve the same goal.  Basically a way to get access to feed data without all the difficult and painful issues of crawling or parsing.

The problem with the Google Feed API though is that you have to know the feed before hand. We mostly deal with BULK access right now.  250k feeds, 1M feeds. etc.

What&#039;s really cool is that we have about a 1/2 dozen PhDs using it right now which is kind of fun.</description>
		<content:encoded><![CDATA[<p>This has actually been available for a while.  It just wasn&#8217;t really obvious.</p>
<p>We have a lot of people using Spinn3r for similar purposes and solve the same goal.  Basically a way to get access to feed data without all the difficult and painful issues of crawling or parsing.</p>
<p>The problem with the Google Feed API though is that you have to know the feed before hand. We mostly deal with BULK access right now.  250k feeds, 1M feeds. etc.</p>
<p>What&#8217;s really cool is that we have about a 1/2 dozen PhDs using it right now which is kind of fun.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Marr</title>
		<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api/comment-page-1#comment-249576</link>
		<dc:creator>Richard Marr</dc:creator>
		<pubDate>Thu, 19 Apr 2007 08:50:01 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2321#comment-249576</guid>
		<description>Guys, they&#039;re not using AJAX, so there is no domain constraint. The only reason you need a proxy is to convert the RSS/whatever into Javascript.

Moreover Technologies (bought by Verisign a while back) has been doing this exact thing for years, except in any output format you like and with a contextual advert added at the top.</description>
		<content:encoded><![CDATA[<p>Guys, they&#8217;re not using AJAX, so there is no domain constraint. The only reason you need a proxy is to convert the RSS/whatever into Javascript.</p>
<p>Moreover Technologies (bought by Verisign a while back) has been doing this exact thing for years, except in any output format you like and with a contextual advert added at the top.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben B</title>
		<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api/comment-page-1#comment-249572</link>
		<dc:creator>Ben B</dc:creator>
		<pubDate>Wed, 18 Apr 2007 23:43:22 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2321#comment-249572</guid>
		<description>I think it is great services are coming out but as I wrote here:
http://www.techthoughts.com/techthoughts/2007/04/google_ajax_fee.html
why not charge a fee like S3 and allow people to make services that actually make money. Note the following from the terms of use:

     5.6  You agree that if you use the Feed API to develop a service for
     other users, it must be made accessible to your end users without
     charge.
I would love something like this - much like how S3 provides cheap grid function for small companies - without having the constraints.</description>
		<content:encoded><![CDATA[<p>I think it is great services are coming out but as I wrote here:<br />
<a href="http://www.techthoughts.com/techthoughts/2007/04/google_ajax_fee.html" rel="nofollow">http://www.techthoughts.com/techthoughts/2007/04/google_ajax_fee.html</a><br />
why not charge a fee like S3 and allow people to make services that actually make money. Note the following from the terms of use:</p>
<p>     5.6  You agree that if you use the Feed API to develop a service for<br />
     other users, it must be made accessible to your end users without<br />
     charge.<br />
I would love something like this &#8211; much like how S3 provides cheap grid function for small companies &#8211; without having the constraints.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bud Gibson</title>
		<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api/comment-page-1#comment-249570</link>
		<dc:creator>Bud Gibson</dc:creator>
		<pubDate>Wed, 18 Apr 2007 21:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2321#comment-249570</guid>
		<description>Looks their recent hiring of Mark Pilgrim might have been to support his universal feed parser that probably underlies this offering.</description>
		<content:encoded><![CDATA[<p>Looks their recent hiring of Mark Pilgrim might have been to support his universal feed parser that probably underlies this offering.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edward Ho</title>
		<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api/comment-page-1#comment-249564</link>
		<dc:creator>Edward Ho</dc:creator>
		<pubDate>Wed, 18 Apr 2007 19:05:15 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2321#comment-249564</guid>
		<description>This is really cool! I&#039;ve noticed some people using Pipes to do the same thing, but this is much cleaner and should be much faster. 
-edward</description>
		<content:encoded><![CDATA[<p>This is really cool! I&#8217;ve noticed some people using Pipes to do the same thing, but this is much cleaner and should be much faster.<br />
-edward</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Zyp</title>
		<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api/comment-page-1#comment-249555</link>
		<dc:creator>Kris Zyp</dc:creator>
		<pubDate>Wed, 18 Apr 2007 15:52:19 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2321#comment-249555</guid>
		<description>Using a proxy is certainly not a new idea. It is nice of them to provide a proxy though.</description>
		<content:encoded><![CDATA[<p>Using a proxy is certainly not a new idea. It is nice of them to provide a proxy though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dion Almaer</title>
		<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api/comment-page-1#comment-249553</link>
		<dc:creator>Dion Almaer</dc:creator>
		<pubDate>Wed, 18 Apr 2007 15:35:15 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2321#comment-249553</guid>
		<description>Henry,

They don&#039;t get around the security constraints as they get the feeds through a proxy at Google (which happens to be on a nice fast edge cache).

You can read more at the FAQ: &lt;a href=&quot;http://code.google.com/support/bin/topic.py?topic=11330&quot; rel=&quot;nofollow&quot;&gt;http://code.google.com/support/bin/topic.py?topic=11330&lt;/a&gt;.

Cheers,

Dion</description>
		<content:encoded><![CDATA[<p>Henry,</p>
<p>They don&#8217;t get around the security constraints as they get the feeds through a proxy at Google (which happens to be on a nice fast edge cache).</p>
<p>You can read more at the FAQ: <a href="http://code.google.com/support/bin/topic.py?topic=11330" rel="nofollow">http://code.google.com/support/bin/topic.py?topic=11330</a>.</p>
<p>Cheers,</p>
<p>Dion</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api/comment-page-1#comment-249550</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Wed, 18 Apr 2007 14:45:45 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2321#comment-249550</guid>
		<description>here&#039;s the link: http://code.google.com/apis/ajaxfeeds/</description>
		<content:encoded><![CDATA[<p>here&#8217;s the link: <a href="http://code.google.com/apis/ajaxfeeds/" rel="nofollow">http://code.google.com/apis/ajaxfeeds/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: henry turner</title>
		<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api/comment-page-1#comment-249548</link>
		<dc:creator>henry turner</dc:creator>
		<pubDate>Wed, 18 Apr 2007 14:43:34 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2321#comment-249548</guid>
		<description>So how do they get around the JavaScript security constraints?</description>
		<content:encoded><![CDATA[<p>So how do they get around the JavaScript security constraints?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://ajaxian.com/archives/google-announces-new-ajax-feed-api/comment-page-1#comment-249546</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Wed, 18 Apr 2007 14:26:32 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=2321#comment-249546</guid>
		<description>aha... I was waiting for that to happen... http://braincast.nl/pivot/entry.php?id=23</description>
		<content:encoded><![CDATA[<p>aha&#8230; I was waiting for that to happen&#8230; <a href="http://braincast.nl/pivot/entry.php?id=23" rel="nofollow">http://braincast.nl/pivot/entry.php?id=23</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

