<?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: Why the eGenera Patent is Dangerous</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/server-virtualization/why-the-egenera-patent-is-dangerous/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/server-virtualization/why-the-egenera-patent-is-dangerous/</link>
	<description>A SearchServerVirtualization.com blog</description>
	<pubDate>Sat, 28 Nov 2009 13:38:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Gillian Farquhar</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/why-the-egenera-patent-is-dangerous/#comment-1195</link>
		<dc:creator>Gillian Farquhar</dc:creator>
		<pubDate>Thu, 21 Aug 2008 22:13:48 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/06/20/why-the-egenera-patent-is-dangerous/#comment-1195</guid>
		<description>Joe - while this is a (very) late reply, I'd like to see if we can open up a dialogue, as clearly how we're different and why this patent is valuable and justified is unclear from our filing alone.

I can assure you however, that Egenera is in the business of innovation and driving customer value - not in the business of defending patents or as you say, "stifling competition" (we have plenty!). When we apply for and are granted a patent, it is because our approach, processes, methods and root technologies are unique.

Please contact me if you're interested in a discussion. At the very least, we can open the communication channels in a more positive way.</description>
		<content:encoded><![CDATA[<p>Joe - while this is a (very) late reply, I&#8217;d like to see if we can open up a dialogue, as clearly how we&#8217;re different and why this patent is valuable and justified is unclear from our filing alone.</p>
<p>I can assure you however, that Egenera is in the business of innovation and driving customer value - not in the business of defending patents or as you say, &#8220;stifling competition&#8221; (we have plenty!). When we apply for and are granted a patent, it is because our approach, processes, methods and root technologies are unique.</p>
<p>Please contact me if you&#8217;re interested in a discussion. At the very least, we can open the communication channels in a more positive way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Foran</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/why-the-egenera-patent-is-dangerous/#comment-1194</link>
		<dc:creator>Joe Foran</dc:creator>
		<pubDate>Wed, 27 Jun 2007 13:46:24 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/06/20/why-the-egenera-patent-is-dangerous/#comment-1194</guid>
		<description>Two Corrections I should not about my post: eGenera is incorrect... it's Egenera. In the i- and e- crazy world of ours, I occasionally forget who's put the e in the correct case. Egenera's patent may be a whole lot of obviousness, but at least they aren't following a needs-to-go-away trend. Also, when I mentioned VMotion in terms of DR, my intent was to mention it along with the other two components that make up the Holy Trinity of VMware DR - High Availability and Dynamic Resource Scheduler (DRS). That's what you get for posting something long enough to give yourself writer's cramp... or typer's cramp as it may be.</description>
		<content:encoded><![CDATA[<p>Two Corrections I should not about my post: eGenera is incorrect&#8230; it&#8217;s Egenera. In the i- and e- crazy world of ours, I occasionally forget who&#8217;s put the e in the correct case. Egenera&#8217;s patent may be a whole lot of obviousness, but at least they aren&#8217;t following a needs-to-go-away trend. Also, when I mentioned VMotion in terms of DR, my intent was to mention it along with the other two components that make up the Holy Trinity of VMware DR - High Availability and Dynamic Resource Scheduler (DRS). That&#8217;s what you get for posting something long enough to give yourself writer&#8217;s cramp&#8230; or typer&#8217;s cramp as it may be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Telematique, water and fire.</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/why-the-egenera-patent-is-dangerous/#comment-1193</link>
		<dc:creator>Telematique, water and fire.</dc:creator>
		<pubDate>Fri, 22 Jun 2007 03:14:50 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/06/20/why-the-egenera-patent-is-dangerous/#comment-1193</guid>
		<description>&lt;strong&gt;How Obvious is the eGenera Patent?&lt;/strong&gt;</description>
		<content:encoded><![CDATA[<p>&lt;strong&gt;How Obvious is the eGenera Patent?&lt;/strong&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PC Blade Daily Links 2007-06-21 - PC Blade Daily - Practical News and Views on Centralized Computing</title>
		<link>http://itknowledgeexchange.techtarget.com/server-virtualization/why-the-egenera-patent-is-dangerous/#comment-1192</link>
		<dc:creator>PC Blade Daily Links 2007-06-21 - PC Blade Daily - Practical News and Views on Centralized Computing</dc:creator>
		<pubDate>Thu, 21 Jun 2007 14:13:57 +0000</pubDate>
		<guid isPermaLink="false">http://servervirtualization.blogs.techtarget.com/2007/06/20/why-the-egenera-patent-is-dangerous/#comment-1192</guid>
		<description>[...] Server Virtualization Blog: Why the eGenera Patent is Dangerous &#8220;This is an awesome product because it can greatly improve DR and perhaps make DR more accessible to smaller businesses, but it’s not patent-worthy.&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] Server Virtualization Blog: Why the eGenera Patent is Dangerous &#8220;This is an awesome product because it can greatly improve DR and perhaps make DR more accessible to smaller businesses, but it’s not patent-worthy.&#8221; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->