Thanks for the correction.
Other language API's, such as C and C++ are intended. To the point regarding C and C++, a number of the AMQP 1.0 developers are developing a C/C++ 1.0 kernal that could be use as the basis for a number of different 1.0 implementation.
A major issue with the current draft is that it is written with a very restricted scope; such that, if we were not inclusive with all such particulars of where we would want to pursue Bindings and Mappings prior to proposing the TC, we would be required to recharter the TC to add emergent opportunities. We recognize this as a limitation of this draft. I have agree to work with OASIS to find language that corrects this restrictive nature. This change will be included in the next draft.
I have a small correction… the first meeting date would be in January 2013, not 2012.
Also, one more substantive question - if this has been discussed in the face-to-face meeting, I apologize. What about a C API, and possibly C++? The C API could be further mapped to Perl, Ruby, Python, etc.
-Steve
Steve Huston
Riverace Corporation
Total Lifecycle Support for Your Networked Applications
On Jul 18, 2012, at 11:09 AM, Matthew Arrott wrote:
<AMQP Bindings Technical Committee Charter v_0-01.docx>