<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Proxy servers and federated search</title>
	<link>http://federatedsearchblog.com/2008/02/02/proxy-servers-and-federated-search/</link>
	<description>Covers topics in the federated search field.</description>
	<pubDate>Fri, 16 May 2008 02:53:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Jonathan Rochkind</title>
		<link>http://federatedsearchblog.com/2008/02/02/proxy-servers-and-federated-search/#comment-174</link>
		<dc:creator>Jonathan Rochkind</dc:creator>
		<pubDate>Mon, 04 Feb 2008 23:04:25 +0000</pubDate>
		<guid>http://federatedsearchblog.com/2008/02/02/proxy-servers-and-federated-search/#comment-174</guid>
		<description>It's worth pointing out that any federated search product will ACT AS proxy servers itself, too. 

In the sense that when an end-user executes a search with the federated search product, it is the federated search software on it's server that contacts the actual databases to be searched, not the end-users computer or browser.  

Of course, federated search is not just a simple 'transparent proxy', it is not just ferrying content un-altered between the user and the content/search  provider.  But it's still a proxy of a sort, in between the end-user adn the content/search providers!</description>
		<content:encoded><![CDATA[<p>It&#8217;s worth pointing out that any federated search product will ACT AS proxy servers itself, too. </p>
<p>In the sense that when an end-user executes a search with the federated search product, it is the federated search software on it&#8217;s server that contacts the actual databases to be searched, not the end-users computer or browser.  </p>
<p>Of course, federated search is not just a simple &#8216;transparent proxy&#8217;, it is not just ferrying content un-altered between the user and the content/search  provider.  But it&#8217;s still a proxy of a sort, in between the end-user adn the content/search providers!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
