On Thu, May 6, 2010 at 2:12 PM, Gordon Sim <g...@redhat.com> wrote: > 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, > hi, See my comments in line.
> > 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. > I agree that we need to have an consistent API for all the clients in c++, perl, python, ruby etc..which goes hand in hand with JMS and WCF client APIs. I saw the current APIs for c++ and python clients here[1] which looks great. Having the first version correct is important which should lead to easy maintain and extensible set of client APIs. > > 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. > I brefily looked at [2] which allows us to define various bindings[3] for c++ programs of course including perl. If we get the perl binding correct obviously we can extend that to support the other languages such as python, ruby etc.. (this will also let us to maintain only swig bindings for c++ clients without maintaining native clients as we use to do now, for ex: python, ruby). So as a POC I'll first look at how to implement the perl binding for C++ clients keeping the same API[1]. I'll keep the list update. Rajika [1] - http://qpid.apache.org/docs/api/ [2] - http://www.swig.org/ [3] - http://www.swig.org/compat.html#SupportedLanguages > > --Gordon. > > [1] http://www.swig.org/ > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > -- http://rajikak.blogspot.com/
