<?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: Microsoft Embraces AMQP Messaging Standard</title>
	<atom:link href="http://thevalerios.net/matt/2008/11/microsoft-embraces-amqp-messaging-standard/feed/" rel="self" type="application/rss+xml" />
	<link>http://thevalerios.net/matt/2008/11/microsoft-embraces-amqp-messaging-standard/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sun, 29 Aug 2010 20:17:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: alexis</title>
		<link>http://thevalerios.net/matt/2008/11/microsoft-embraces-amqp-messaging-standard/comment-page-1/#comment-4056</link>
		<dc:creator>alexis</dc:creator>
		<pubDate>Tue, 25 Nov 2008 15:46:47 +0000</pubDate>
		<guid isPermaLink="false">http://thevalerios.net/matt/2008/11/microsoft-embraces-amqp-messaging-standard/#comment-4056</guid>
		<description>People can now run RabbitMQ as a Windows service, meeting Matt&#039;s requirement above.  Any questions please email info at rabbitmq dot com.  Cheers, alexis</description>
		<content:encoded><![CDATA[<p>People can now run RabbitMQ as a Windows service, meeting Matt&#8217;s requirement above.  Any questions please email info at rabbitmq dot com.  Cheers, alexis</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://thevalerios.net/matt/2008/11/microsoft-embraces-amqp-messaging-standard/comment-page-1/#comment-3440</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Fri, 07 Nov 2008 14:13:15 +0000</pubDate>
		<guid isPermaLink="false">http://thevalerios.net/matt/2008/11/microsoft-embraces-amqp-messaging-standard/#comment-3440</guid>
		<description>dsmith -- You&#039;re right, I should have mentioned the Erlang server.  For what it&#039;s worth, I downloaded the RabbitMQ server &quot;bundle&quot; and had it up and running on the command line in less than 5 minutes. In the future it might be nice to see a wrapper around the server application so that it can be started/stopped from the management console.</description>
		<content:encoded><![CDATA[<p>dsmith &#8212; You&#8217;re right, I should have mentioned the Erlang server.  For what it&#8217;s worth, I downloaded the RabbitMQ server &#8220;bundle&#8221; and had it up and running on the command line in less than 5 minutes. In the future it might be nice to see a wrapper around the server application so that it can be started/stopped from the management console.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dsmith</title>
		<link>http://thevalerios.net/matt/2008/11/microsoft-embraces-amqp-messaging-standard/comment-page-1/#comment-3437</link>
		<dc:creator>dsmith</dc:creator>
		<pubDate>Fri, 07 Nov 2008 06:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://thevalerios.net/matt/2008/11/microsoft-embraces-amqp-messaging-standard/#comment-3437</guid>
		<description>AMQP is very promising from a standardization point-of-view and RabbitMQ is an excellent implementation, but the RabbitMQ server is written on top of Erlang/OTP - not .NET.  The RabbitMQ .NET package is simply a client library. 

This shouldn&#039;t discourage anyone. Erlang/OTP has a proven track record as a foundation for scalable, fault tolerant systems.  It has been used for 20 years in the telecom industry and has recently grown in popularity to be used inseveral high profile projects including ejabberd and CouchDB.</description>
		<content:encoded><![CDATA[<p>AMQP is very promising from a standardization point-of-view and RabbitMQ is an excellent implementation, but the RabbitMQ server is written on top of Erlang/OTP &#8211; not .NET.  The RabbitMQ .NET package is simply a client library. </p>
<p>This shouldn&#8217;t discourage anyone. Erlang/OTP has a proven track record as a foundation for scalable, fault tolerant systems.  It has been used for 20 years in the telecom industry and has recently grown in popularity to be used inseveral high profile projects including ejabberd and CouchDB.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://thevalerios.net/matt/2008/11/microsoft-embraces-amqp-messaging-standard/comment-page-1/#comment-3432</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Thu, 06 Nov 2008 19:18:08 +0000</pubDate>
		<guid isPermaLink="false">http://thevalerios.net/matt/2008/11/microsoft-embraces-amqp-messaging-standard/#comment-3432</guid>
		<description>It IS huge!  I spent part of my summer making a pub/sub system with WCF and it was a ton of work, but it didn&#039;t even address things like reliability or throttling (basically the equivalent of UDP compared to TCP).  Really looking forward to trying RabbitMQ out.</description>
		<content:encoded><![CDATA[<p>It IS huge!  I spent part of my summer making a pub/sub system with WCF and it was a ton of work, but it didn&#8217;t even address things like reliability or throttling (basically the equivalent of UDP compared to TCP).  Really looking forward to trying RabbitMQ out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Noonen</title>
		<link>http://thevalerios.net/matt/2008/11/microsoft-embraces-amqp-messaging-standard/comment-page-1/#comment-3431</link>
		<dc:creator>Nate Noonen</dc:creator>
		<pubDate>Thu, 06 Nov 2008 19:11:04 +0000</pubDate>
		<guid isPermaLink="false">http://thevalerios.net/matt/2008/11/microsoft-embraces-amqp-messaging-standard/#comment-3431</guid>
		<description>Huge.  I am working on a project that uses MSMQ and a custom implementation by the customer.  It&#039;s actually pretty cool, but there are a lot of issues with permissions on queues. We are using the publish subscribe method and it seems to be fairly solid, but the permission sets and the difficulty in the underlying implementation (it took a long time to get it sufficiently architected) makes me excited for a built in version for .NET.</description>
		<content:encoded><![CDATA[<p>Huge.  I am working on a project that uses MSMQ and a custom implementation by the customer.  It&#8217;s actually pretty cool, but there are a lot of issues with permissions on queues. We are using the publish subscribe method and it seems to be fairly solid, but the permission sets and the difficulty in the underlying implementation (it took a long time to get it sufficiently architected) makes me excited for a built in version for .NET.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
