THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Incomplete
This table is a work-in-progress and should considered neither complete nor correct at this point.
Join In
I have started a thread about this table on the dev mailing list - "0.6 Feature Matrix". Let us know what you think!
1. Related Pages
0.6 Feature Matrix
0.6 Feature Descriptions
2. AMQP Interoperability
| Brokers | |||||
|---|---|---|---|---|---|
| C++ | Java | ||||
| Linux | Windows | * | |||
| Clients | C++ | Linux | 0-10 | 0-10 | 0-10 |
| Windows | 0-10 | 0-10 | 0-10 | ||
| JMS | * | 0-10 | 0-10 | 0-8 0-9 0-9-1 0-10 |
|
| Python | * | 0-10 | 0-10 | 0-8 0-9 0-9-1 0-10 |
|
| Ruby | * | 0-10 | 0-10 | 0-8 0-9 0-9-1 0-10 |
|
| WCF | Windows | 0-10 | 0-10 | 0-10 | |
3. Feature Interoperability
Feature Interoperability
We need a matrix which addresses feature interoperability across implementations. For instance, if the Java broker has clustering, will the JMS client support cluster failover on a C++ broker? (and visa versa). What about Python and Ruby?