Aidan Skinner wrote:
It's particularly important where we're importing something which
duplicates (fully or partially) existing functionality, if only so
that the situation is sufficiently clear to people trying to make an
informed decision about what best suits their needs.
Perhaps the QPID project itself could focus on just C++ for all the
protocol handling and use swig (or similar) to create wrappers, so the
code volume to support multiple client languages will be much smaller.
Then native clients can be completely independant projects.
AMQP is supposed to be interoperable on the wire: there shouldn't be a
requirement for QPID to provide a lot of native client support, though
some scripting (for some definition of that term) is clearly handy for
testing etc.
James
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
