<?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: A Peek Inside: Why no cross-farm support?</title>
	<atom:link href="http://powerpivotgeek.com/2009/11/25/a-peek-inside-why-no-cross-farm-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://powerpivotgeek.com/2009/11/25/a-peek-inside-why-no-cross-farm-support/</link>
	<description>An adventure in managed self-service computing</description>
	<lastBuildDate>Mon, 16 Apr 2012 21:38:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: A Peek Inside: Why no cross-farm support? &#171; PowerPivot Twins!</title>
		<link>http://powerpivotgeek.com/2009/11/25/a-peek-inside-why-no-cross-farm-support/comment-page-1/#comment-200</link>
		<dc:creator>A Peek Inside: Why no cross-farm support? &#171; PowerPivot Twins!</dc:creator>
		<pubDate>Tue, 05 Jan 2010 04:08:34 +0000</pubDate>
		<guid isPermaLink="false">http://powerpivotgeek.com/?p=410#comment-200</guid>
		<description>[...] Read more&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Read more&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: powerpivotgeek</title>
		<link>http://powerpivotgeek.com/2009/11/25/a-peek-inside-why-no-cross-farm-support/comment-page-1/#comment-97</link>
		<dc:creator>powerpivotgeek</dc:creator>
		<pubDate>Sat, 05 Dec 2009 06:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://powerpivotgeek.com/?p=410#comment-97</guid>
		<description>Hi Marc. Absolutely correct. We could have invented our own remoting infrastructure. We considered that option. However we would then have to own, maintain, support and enhance it. We had extensive meetings with several of the SharePoint teams that have similar requirements to our, such as the Excel Services group. Ultimately we all came to the same conclusion that this is a problem that is best addressed by the SharePoint OM infrastructure itself rather than each of us having to write our own code.
BTW: Nice avatar.</description>
		<content:encoded><![CDATA[<p>Hi Marc. Absolutely correct. We could have invented our own remoting infrastructure. We considered that option. However we would then have to own, maintain, support and enhance it. We had extensive meetings with several of the SharePoint teams that have similar requirements to our, such as the Excel Services group. Ultimately we all came to the same conclusion that this is a problem that is best addressed by the SharePoint OM infrastructure itself rather than each of us having to write our own code.<br />
BTW: Nice avatar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Brooks</title>
		<link>http://powerpivotgeek.com/2009/11/25/a-peek-inside-why-no-cross-farm-support/comment-page-1/#comment-96</link>
		<dc:creator>Marc Brooks</dc:creator>
		<pubDate>Fri, 04 Dec 2009 22:42:04 +0000</pubDate>
		<guid isPermaLink="false">http://powerpivotgeek.com/?p=410#comment-96</guid>
		<description>I&#039;m a SharePoint and PowerPivot neophyte, but it seems to me that this is yet another place where the problem could be solved by one more level of indirection.  When a PowerPivot is constructed, a proxy object could be materialized INSIDE the PowerPivot farm that merely indirects out to the original content farm. It could even copy down the referenced data and setup an in-farm cache.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a SharePoint and PowerPivot neophyte, but it seems to me that this is yet another place where the problem could be solved by one more level of indirection.  When a PowerPivot is constructed, a proxy object could be materialized INSIDE the PowerPivot farm that merely indirects out to the original content farm. It could even copy down the referenced data and setup an in-farm cache.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

