I think it would be more worthwhile to try to synchronize the APIs
between the languages.
i.e. make the python/C++ APIs look more alike. Obviously there are
language differences, so they won't be identical. I think it would be
beneficial if you could expect that the class structure would be similar
and methods found in the Java AMQP native API would be present in C++
and Python.
//Bill
On 09/14/2009 02:23 PM, Rafael Schloming wrote:
Jonathan Robie wrote:
Do we want the new messaging API to be useful for other messaging
systems that are not based on AMQP, or is that a non-goal?
So far the primary goal has been to be useful to applications, which
means the API inevitably includes support for functionality that isn't
necessarily present in the lowest common denominator messaging
systems. However this doesn't mean you couldn't use the API with other
messaging systems if you avoided depending on those features. For
example you could implement an SMTP/POP based backend, but you would
need to throw an exception if someone tried to create a transactional
session.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
