On 05/01/2010 01:14 AM, Rajika Kumarasiri wrote:
I see that in your TODO list [1], you have listed writing perl clients as
one of the new features that you'd like to see. I'd like to know if anybody
work on this? If not I can come with a proposal to add that support.
Hi Rajika,
I'm not aware of any work on that to date.
We are aiming to get as much conceptual consistency as possible between
clients in the different languages. Where there already exists an
obvious API in the target language (JMS, WCF) we obviously support that.
Where there is no such API we want to ensure that the APIs we define are
conceptually similar to make the project work well as a whole. We have
defined such an API in the messaging namespace/module for c++ and python
(ruby to follow) and I think any perl client should follow that model.
Ensuring that as a community we are able to maintain a new client going
forward is as important as getting the first version of the code. In
this context I think it would be worth exploring whether e.g. the c++
version could be swigged[1] to allow access from perl.
--Gordon.
[1] http://www.swig.org/
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
