<?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: Choosing a JMS Provider: Harder than it should be</title>
	<atom:link href="http://alterlabs.com/technologies/java/choosing-a-jms-provider-harder-than-it-should-be/feed/" rel="self" type="application/rss+xml" />
	<link>http://alterlabs.com/technologies/java/choosing-a-jms-provider-harder-than-it-should-be/</link>
	<description>Results through imagination</description>
	<lastBuildDate>Mon, 15 Mar 2010 02:56:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: don</title>
		<link>http://alterlabs.com/technologies/java/choosing-a-jms-provider-harder-than-it-should-be/comment-page-1/#comment-10</link>
		<dc:creator>don</dc:creator>
		<pubDate>Mon, 13 Mar 2006 14:43:30 +0000</pubDate>
		<guid isPermaLink="false">http://alterlabs.com/java/choosing-a-jms-provider-harder-than-it-should-be/#comment-10</guid>
		<description>Thanks for all the suggestions and info from the comments. As was noted in an earlier post, this evaluation (at the clients request) is currently limited to conventional commercial vendors, but ultimately may not be (they make heavy use of jBoss and MySql, for example, so they are no strangers to OpenSource in the enterprise.)  It will likely be a week or two before the dust settles, but I will update this post with ultimate results of the survey.</description>
		<content:encoded><![CDATA[<p>Thanks for all the suggestions and info from the comments. As was noted in an earlier post, this evaluation (at the clients request) is currently limited to conventional commercial vendors, but ultimately may not be (they make heavy use of jBoss and MySql, for example, so they are no strangers to OpenSource in the enterprise.)  It will likely be a week or two before the dust settles, but I will update this post with ultimate results of the survey.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Richardson</title>
		<link>http://alterlabs.com/technologies/java/choosing-a-jms-provider-harder-than-it-should-be/comment-page-1/#comment-9</link>
		<dc:creator>Mike Richardson</dc:creator>
		<pubDate>Sun, 12 Mar 2006 19:19:01 +0000</pubDate>
		<guid isPermaLink="false">http://alterlabs.com/java/choosing-a-jms-provider-harder-than-it-should-be/#comment-9</guid>
		<description>Mark,

Thanks for the suggestions.  I am doing some testing right now with ActiveMQ and I have to say it is pretty nice.  Now its time to put a .NET wrapper around this sucker!  :-)

- Mike</description>
		<content:encoded><![CDATA[<p>Mark,</p>
<p>Thanks for the suggestions.  I am doing some testing right now with ActiveMQ and I have to say it is pretty nice.  Now its time to put a .NET wrapper around this sucker!  :-)</p>
<p>- Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Nickel</title>
		<link>http://alterlabs.com/technologies/java/choosing-a-jms-provider-harder-than-it-should-be/comment-page-1/#comment-8</link>
		<dc:creator>Mark Nickel</dc:creator>
		<pubDate>Sun, 12 Mar 2006 15:07:23 +0000</pubDate>
		<guid isPermaLink="false">http://alterlabs.com/java/choosing-a-jms-provider-harder-than-it-should-be/#comment-8</guid>
		<description>There is support for REST, but you should probably check out this posting in the forums before getting too excited:

http://forums.activemq.org/posts/list/143.page

IMO, the REST support in ActiveMQ is really in place so that you could implement a new client in a non-Java language.  From my experimentation, using the REST interface is fairly complex...  But that&#039;s definitely not the fault of ActiveMQ.  :)

For easier scripting you are probably going to want to play with STOMP or the AJAX as these build on the REST and hide the complexities of how REST is implemented within ActiveMQ.

I think it&#039;s great to have these simpler clients that hide the majority of the gritty details of a JMS client.  Most implementations really just need to send and receive messages...  The infrastructure should take care of the details...   If you really need the low level stuff for nailing that last few percentage points of performance, you can do it because the details are still available.</description>
		<content:encoded><![CDATA[<p>There is support for REST, but you should probably check out this posting in the forums before getting too excited:</p>
<p><a href="http://forums.activemq.org/posts/list/143.page" rel="nofollow">http://forums.activemq.org/posts/list/143.page</a></p>
<p>IMO, the REST support in ActiveMQ is really in place so that you could implement a new client in a non-Java language.  From my experimentation, using the REST interface is fairly complex&#8230;  But that&#8217;s definitely not the fault of ActiveMQ.  :)</p>
<p>For easier scripting you are probably going to want to play with STOMP or the AJAX as these build on the REST and hide the complexities of how REST is implemented within ActiveMQ.</p>
<p>I think it&#8217;s great to have these simpler clients that hide the majority of the gritty details of a JMS client.  Most implementations really just need to send and receive messages&#8230;  The infrastructure should take care of the details&#8230;   If you really need the low level stuff for nailing that last few percentage points of performance, you can do it because the details are still available.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Richardson</title>
		<link>http://alterlabs.com/technologies/java/choosing-a-jms-provider-harder-than-it-should-be/comment-page-1/#comment-7</link>
		<dc:creator>Mike Richardson</dc:creator>
		<pubDate>Sun, 12 Mar 2006 00:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://alterlabs.com/java/choosing-a-jms-provider-harder-than-it-should-be/#comment-7</guid>
		<description>Bruce,

Interesting point - I am definitely interested and am going to download it now to run some basic performance tests.  I am also very interested in its support of the REST protocol, which could make for some interesting messaging scenarios.</description>
		<content:encoded><![CDATA[<p>Bruce,</p>
<p>Interesting point &#8211; I am definitely interested and am going to download it now to run some basic performance tests.  I am also very interested in its support of the REST protocol, which could make for some interesting messaging scenarios.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Snyder</title>
		<link>http://alterlabs.com/technologies/java/choosing-a-jms-provider-harder-than-it-should-be/comment-page-1/#comment-6</link>
		<dc:creator>Bruce Snyder</dc:creator>
		<pubDate>Sat, 11 Mar 2006 17:40:01 +0000</pubDate>
		<guid isPermaLink="false">http://alterlabs.com/java/choosing-a-jms-provider-harder-than-it-should-be/#comment-6</guid>
		<description>ActiveMQ 4.0 supports all of your requirements and more, without any license costs because it is Apache Licensed open source. Services and support can be purchased from LogicBlaze (http://www.logicblaze.com/). In addition, ActiveMQ outperforms nearly all other JMS implementations, most by a large margin - see the performance report here: 

http://logicblaze.com/AMQ_data_sheet.pdf</description>
		<content:encoded><![CDATA[<p>ActiveMQ 4.0 supports all of your requirements and more, without any license costs because it is Apache Licensed open source. Services and support can be purchased from LogicBlaze (<a href="http://www.logicblaze.com/" rel="nofollow">http://www.logicblaze.com/</a>). In addition, ActiveMQ outperforms nearly all other JMS implementations, most by a large margin &#8211; see the performance report here: </p>
<p><a href="http://logicblaze.com/AMQ_data_sheet.pdf" rel="nofollow">http://logicblaze.com/AMQ_data_sheet.pdf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Richardson</title>
		<link>http://alterlabs.com/technologies/java/choosing-a-jms-provider-harder-than-it-should-be/comment-page-1/#comment-5</link>
		<dc:creator>Mike Richardson</dc:creator>
		<pubDate>Sat, 11 Mar 2006 15:10:20 +0000</pubDate>
		<guid isPermaLink="false">http://alterlabs.com/java/choosing-a-jms-provider-harder-than-it-should-be/#comment-5</guid>
		<description>To everyone that is reading this post/and comments:  if you have experience using queuing vendors for .NET messaging applications other than MSMQ, please give me some information on your experiences with other vendors.  MQ Series is a wonderful product, but there .NET API is terrible.  As a matter of fact, just to implement transactions requires the use of COM+ interop (not good).  Sonic suffers from the same issue.  I am currently testing the .NET API with Tibco Rendevous and it looks pretty useful so far.  As soon as I am done my functional and performance testing, I will be posting my results.</description>
		<content:encoded><![CDATA[<p>To everyone that is reading this post/and comments:  if you have experience using queuing vendors for .NET messaging applications other than MSMQ, please give me some information on your experiences with other vendors.  MQ Series is a wonderful product, but there .NET API is terrible.  As a matter of fact, just to implement transactions requires the use of COM+ interop (not good).  Sonic suffers from the same issue.  I am currently testing the .NET API with Tibco Rendevous and it looks pretty useful so far.  As soon as I am done my functional and performance testing, I will be posting my results.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damien</title>
		<link>http://alterlabs.com/technologies/java/choosing-a-jms-provider-harder-than-it-should-be/comment-page-1/#comment-4</link>
		<dc:creator>Damien</dc:creator>
		<pubDate>Sat, 11 Mar 2006 05:42:39 +0000</pubDate>
		<guid isPermaLink="false">http://alterlabs.com/java/choosing-a-jms-provider-harder-than-it-should-be/#comment-4</guid>
		<description>Oops, I missed the part where you said commercial.  If by that you mean; pay for software license and professional services, as opposed to open source software and pay for professional services....  Well, then good luck with that.</description>
		<content:encoded><![CDATA[<p>Oops, I missed the part where you said commercial.  If by that you mean; pay for software license and professional services, as opposed to open source software and pay for professional services&#8230;.  Well, then good luck with that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damien</title>
		<link>http://alterlabs.com/technologies/java/choosing-a-jms-provider-harder-than-it-should-be/comment-page-1/#comment-3</link>
		<dc:creator>Damien</dc:creator>
		<pubDate>Sat, 11 Mar 2006 05:39:27 +0000</pubDate>
		<guid isPermaLink="false">http://alterlabs.com/java/choosing-a-jms-provider-harder-than-it-should-be/#comment-3</guid>
		<description>I highly recommend JORAM --&gt; http://joram.objectweb.org/</description>
		<content:encoded><![CDATA[<p>I highly recommend JORAM &#8211;&gt; <a href="http://joram.objectweb.org/" rel="nofollow">http://joram.objectweb.org/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ks</title>
		<link>http://alterlabs.com/technologies/java/choosing-a-jms-provider-harder-than-it-should-be/comment-page-1/#comment-2</link>
		<dc:creator>ks</dc:creator>
		<pubDate>Sat, 11 Mar 2006 05:34:56 +0000</pubDate>
		<guid isPermaLink="false">http://alterlabs.com/java/choosing-a-jms-provider-harder-than-it-should-be/#comment-2</guid>
		<description>Did you try TIBCO EMS? http://www.tibco.com/software/enterprise_backbone/enterprisemessageservice.jsp</description>
		<content:encoded><![CDATA[<p>Did you try TIBCO EMS? <a href="http://www.tibco.com/software/enterprise_backbone/enterprisemessageservice.jsp" rel="nofollow">http://www.tibco.com/software/enterprise_backbone/enterprisemessageservice.jsp</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
