[openamq-dev] Spec conformance chart? Shopping for a new broker

[Brad Clements]

Hi, Thanks for the response

Pieter Hintjens wrote:
> On Fri, May 9, 2008 at 6:44 PM, Brad Clements <bkc at murkworks.com> wrote:
>
>   
>>  It would be helfpul for me to have some kind of "spec conformance" chart
>>  for OpenAMQ. Something like http://www.rabbitmq.com/compatibility.html
>>  but doesn't have to be so fancy.
>>     
>
> http://www.openamq.org/features.html
>   
I did look at the features list, but it's not entirely clear how each 
"feature" maps to a specific element of the AMQP specification.

Also it doesn't say which AMQP specification is implemented. I'm 
guessing it's 0.9 based on looking at the mailing list.

Here's another example of what I find super helpful when determining 
which features are in a project and which ones are not yet implemented:

http://www.mozilla.org/projects/xforms/status-detail.html

Its very very helpful to know *exactly* what's implemented, what's 
planned (even if it's planned for the far future)..

>   
>>  For example, does OpenAMQ support file or stream class?
>>     
>
> Nope.
>   
Ok. so the next  questions would be .. Are these on the roadmap for .. 
2009, or "never"?
>   
>
> REST is fun, but I suspect how you implement that is orthogonal to
> what messaging technology you use.  
I agree completely. I mentioned what I was planning to do just to 
provide some context.

Even if you do implement some kind of REST-like HTTP interface, my 
authentication needs probably would not overlap w/ what you're doing 
anyway.

-B


-- 
Brad Clements,                bkc at murkworks.com    (315)268-1000
http://www.murkworks.com                          
AOL-IM: BKClements

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openamq.org/pipermail/openamq-dev/attachments/20080509/dfc03750/attachment.htm