<?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: The Future of BizTalk/WCF/WF</title>
	<atom:link href="http://winterdom.com/2007/09/thefutureofbiztalkwcfwf/feed" rel="self" type="application/rss+xml" />
	<link>http://winterdom.com/2007/09/thefutureofbiztalkwcfwf</link>
	<description>by dæmons be driven</description>
	<lastBuildDate>Tue, 16 Mar 2010 06:33:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sam Vanhoutte</title>
		<link>http://winterdom.com/2007/09/thefutureofbiztalkwcfwf/comment-page-1#comment-219</link>
		<dc:creator>Sam Vanhoutte</dc:creator>
		<pubDate>Thu, 20 Sep 2007 07:17:15 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2007/09/thefutureofbiztalkwcfwf#comment-219</guid>
		<description>Nice post Thomas.
I think a lot of guessing will be done for a while, but most of the issues and thinking you have make sense.
I definitely agree on the migration path that is extremely important, since BizTalk is typically used in mission-critical long term enterprise wide projects, and IT managers really need to get this guarantee.
What we are also feeling is that Microsoft is moving more and more BizTalk functionality to the framework or to seperate packages (ie. WCF LOB adapters).  Could we imagine to see mapping, pipeline components, flat file parsing... to move to the vNext framework?
If this would be the case the only (but very important!) advantage of BizTalk Server compared to the framework would be the enterprise ready scalable high performant host. (with tracking etc...)
Time will tell ;-)
</description>
		<content:encoded><![CDATA[<p>Nice post Thomas.<br />
I think a lot of guessing will be done for a while, but most of the issues and thinking you have make sense.<br />
I definitely agree on the migration path that is extremely important, since BizTalk is typically used in mission-critical long term enterprise wide projects, and IT managers really need to get this guarantee.<br />
What we are also feeling is that Microsoft is moving more and more BizTalk functionality to the framework or to seperate packages (ie. WCF LOB adapters).  Could we imagine to see mapping, pipeline components, flat file parsing&#8230; to move to the vNext framework?<br />
If this would be the case the only (but very important!) advantage of BizTalk Server compared to the framework would be the enterprise ready scalable high performant host. (with tracking etc&#8230;)<br />
Time will tell <img src='http://winterdom.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leonid Ganeline</title>
		<link>http://winterdom.com/2007/09/thefutureofbiztalkwcfwf/comment-page-1#comment-218</link>
		<dc:creator>Leonid Ganeline</dc:creator>
		<pubDate>Wed, 19 Sep 2007 11:45:53 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2007/09/thefutureofbiztalkwcfwf#comment-218</guid>
		<description>Great article!
I think the lightweight MessgeBox Engine in the v.Next is quite possible. It would be really good to support synchronous WCF features. And possible the WCF WS-* security stuff can be implemented much more easily then now in BizTalk.
BTW What about ESS-service? Now BizTalk has not to much to propose on the security area.
Regards,
Leonid Ganeline [BizTalk MVP]
http://geekswithblogs.net/leonidganeline/
</description>
		<content:encoded><![CDATA[<p>Great article!<br />
I think the lightweight MessgeBox Engine in the v.Next is quite possible. It would be really good to support synchronous WCF features. And possible the WCF WS-* security stuff can be implemented much more easily then now in BizTalk.<br />
BTW What about ESS-service? Now BizTalk has not to much to propose on the security area.<br />
Regards,<br />
Leonid Ganeline [BizTalk MVP]<br />
<a href="http://geekswithblogs.net/leonidganeline/" rel="nofollow">http://geekswithblogs.net/leonidganeline/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walter Michel</title>
		<link>http://winterdom.com/2007/09/thefutureofbiztalkwcfwf/comment-page-1#comment-217</link>
		<dc:creator>Walter Michel</dc:creator>
		<pubDate>Sun, 09 Sep 2007 16:12:54 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2007/09/thefutureofbiztalkwcfwf#comment-217</guid>
		<description>Hi Tomas,
Thanks for sharing your thoughts on the future BT/WCF/WF.  Your article gives us many good things to think about.  And you are quite right in that everyone (especially me) should get up to speed on WF and WCF.
I mainly work on EAI and B2Bi solutions.  It seems to me that if Microsoft wants to remain a player in this arena it really need to retain many of the capabilities of BizTalk.  You mentioned that BizTalk is message oriented.  I believe that EAI and B2Bi tools really need to support many message oriented patterns and practices in order to be effective.  MS will either have to hang on to BT or overhaul WF and WCF to provide the features necessary to implement message based architectures.  I am definitely very keen to see how things play out... :)
Walter
</description>
		<content:encoded><![CDATA[<p>Hi Tomas,<br />
Thanks for sharing your thoughts on the future BT/WCF/WF.  Your article gives us many good things to think about.  And you are quite right in that everyone (especially me) should get up to speed on WF and WCF.<br />
I mainly work on EAI and B2Bi solutions.  It seems to me that if Microsoft wants to remain a player in this arena it really need to retain many of the capabilities of BizTalk.  You mentioned that BizTalk is message oriented.  I believe that EAI and B2Bi tools really need to support many message oriented patterns and practices in order to be effective.  MS will either have to hang on to BT or overhaul WF and WCF to provide the features necessary to implement message based architectures.  I am definitely very keen to see how things play out&#8230; <img src='http://winterdom.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
Walter</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Restrepo</title>
		<link>http://winterdom.com/2007/09/thefutureofbiztalkwcfwf/comment-page-1#comment-216</link>
		<dc:creator>Tomas Restrepo</dc:creator>
		<pubDate>Mon, 03 Sep 2007 19:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2007/09/thefutureofbiztalkwcfwf#comment-216</guid>
		<description>Jon: Well, you know much more than me about BizTalk and WF, and you wrote *the* sample about integrating WF with BizTalk orchestrations. In my book, that makes you pretty qualified for an educated guess :)
</description>
		<content:encoded><![CDATA[<p>Jon: Well, you know much more than me about BizTalk and WF, and you wrote *the* sample about integrating WF with BizTalk orchestrations. In my book, that makes you pretty qualified for an educated guess <img src='http://winterdom.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Flanders</title>
		<link>http://winterdom.com/2007/09/thefutureofbiztalkwcfwf/comment-page-1#comment-215</link>
		<dc:creator>Jon Flanders</dc:creator>
		<pubDate>Mon, 03 Sep 2007 19:31:27 +0000</pubDate>
		<guid isPermaLink="false">http://winterdom.com/2007/09/thefutureofbiztalkwcfwf#comment-215</guid>
		<description>Nice post Tomas.  The part about me is flattering - but I am not sure its true ;-).  I&#039;m pretty sure I am guessing just as much as the next guy.
</description>
		<content:encoded><![CDATA[<p>Nice post Tomas.  The part about me is flattering &#8211; but I am not sure its true <img src='http://winterdom.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> .  I&#8217;m pretty sure I am guessing just as much as the next guy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
