<?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: Gurock Software partners with EurekaLab</title>
	<atom:link href="http://blog.gurock.com/postings/gurock-software-partners-with-eurekalab/259/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gurock.com/postings/gurock-software-partners-with-eurekalab/259/</link>
	<description>Our products, programming &#38; business.</description>
	<lastBuildDate>Wed, 18 Jan 2012 21:41:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Dennis Gurock</title>
		<link>http://blog.gurock.com/postings/gurock-software-partners-with-eurekalab/259/comment-page-1/#comment-4015</link>
		<dc:creator>Dennis Gurock</dc:creator>
		<pubDate>Mon, 04 Jun 2007 15:28:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/postings/gurock-software-partners-with-eurekalab/259/#comment-4015</guid>
		<description>Hello Shawn,

You can use madExcept together with SmartInspect without any limitations (including the memory protocol) and in fact, we haven&#039;t built anything special for EurekaLog. The partnership focuses on promoting each others tools, but there is nothing that prevents madExcept users from using SmartInspect (and we support this, too, of course). Here is a quick introduction to the memory protocol of SmartInspect and more is available in our online documentation:

http://blog.gurock.com/postings/new-memory-protocol-in-smartinspect-20/229/</description>
		<content:encoded><![CDATA[<p>Hello Shawn,</p>
<p>You can use madExcept together with SmartInspect without any limitations (including the memory protocol) and in fact, we haven&#8217;t built anything special for EurekaLog. The partnership focuses on promoting each others tools, but there is nothing that prevents madExcept users from using SmartInspect (and we support this, too, of course). Here is a quick introduction to the memory protocol of SmartInspect and more is available in our online documentation:</p>
<p><a href="http://blog.gurock.com/postings/new-memory-protocol-in-smartinspect-20/229/" rel="nofollow">http://blog.gurock.com/postings/new-memory-protocol-in-smartinspect-20/229/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn Oster</title>
		<link>http://blog.gurock.com/postings/gurock-software-partners-with-eurekalab/259/comment-page-1/#comment-4014</link>
		<dc:creator>Shawn Oster</dc:creator>
		<pubDate>Mon, 04 Jun 2007 15:07:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/postings/gurock-software-partners-with-eurekalab/259/#comment-4014</guid>
		<description>Any chance of functionality like this for madExcept?  I have nothing against EurekaLog, I&#039;ve just been using madExcept for so long that I&#039;d prefer not having to swap everything out.</description>
		<content:encoded><![CDATA[<p>Any chance of functionality like this for madExcept?  I have nothing against EurekaLog, I&#8217;ve just been using madExcept for so long that I&#8217;d prefer not having to swap everything out.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

