Warning |
---|
|
This table is a work-in-progress and should considered neither complete nor correct at this point. |
Tip |
---|
|
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
HTML |
---|
<table border="1">
<tr>
<th rowspan="3" colspan="3"> </th>
<th colspan="3" bgcolor="#e0e0e0">Brokers</th>
</tr>
<tr>
<th colspan="2" bgcolor="#e0e0e0">C++</th>
<th bgcolor="#e0e0e0">Java</th>
</tr>
<tr>
<th bgcolor="#e0e0e0">Linux</th>
<th bgcolor="#e0e0e0">Windows</th>
<th bgcolor="#e0e0e0">*</th>
</tr>
<tr>
<th rowspan="6" bgcolor="#e0e0e0">Clients</th>
<th rowspan="2" bgcolor="#e0e0e0">C++</th>
<th bgcolor="#e0e0e0">Linux</th>
<td>0-10</td>
<td>0-10</td>
<td>0-10</td>
</tr>
<tr>
<th bgcolor="#e0e0e0">Windows</th>
<td>0-10</td>
<td>0-10</td>
<td>0-10</td>
</tr>
<tr>
<th bgcolor="#e0e0e0">JMS</th>
<th bgcolor="#e0e0e0">*</th>
<td>0-10</td>
<td>0-10</td>
<td>0-8<br>0-9<br>0-9-1<br>0-10</td>
</tr>
<tr>
<th bgcolor="#e0e0e0">Python</th>
<th bgcolor="#e0e0e0">*</th>
<td>0-10</td>
<td>0-10</td>
<td>0-8<br>0-9<br>0-9-1<br>0-10</td>
</tr>
<tr>
<th bgcolor="#e0e0e0">Ruby</th>
<th bgcolor="#e0e0e0">*</th>
<td>0-10</td>
<td>0-10</td>
<td>0-8<br>0-9<br>0-9-1<br>0-10</td>
</tr>
<tr>
<th bgcolor="#e0e0e0">WCF</th>
<th bgcolor="#e0e0e0">Windows</th>
<td>0-10</td>
<td>0-10</td>
<td>0-10</td>
</tr>
</table>
|
3. Feature Interoperability
Info |
---|
title | 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? |