On Wed, Jan 26, 2011 at 3:29 PM, Rajith Attapattu <rajit...@gmail.com> wrote: > Hey Paul, > > Thank you very much for your kind comments about Qpid and your desire to > contribute towards the project. > Perhaps it's best to create a separate JIRA for the PHP client.
Will do :) > I am sorry if you are already aware of this, but if you weren't it's best if > the PHP API follows the same model as the new Python and C++ messaging API. > That will make all the clients look and behave the same way. Makes sense - consistency is a valuable thing :) I was (still am) modelling the SWIG interface file on the same one that the existing Python and Ruby bindings use (https://svn.apache.org/repos/asf/qpid/trunk/qpid/cpp/bindings/qpid/qpid.i) - hopefully I can "%include" that file the same way that the other bindings do, so that would basically expose all of the messaging/*.h headers, which if I understand correctly, is the messaging API that you're suggesting. Thanks for the guidance. I look forward to submitting some stuff in a couple of days :) Paul. > > Regards, > > Rajith > > On Tue, Jan 25, 2011 at 10:30 PM, Paul Colby <q...@colby.id.au> wrote: > >> Hi everyone, >> >> First of all, let me just say that I'm really impressed with Qpid! >> I've been playing with the C++ broker and client library on and off >> for the past couple of weeks, and I've been continually impressed with >> just how well it works out of the box. So thank you all!! :) >> >> As well as C++, I am quite interested in using Qpid from PHP, and so >> I've been experimenting with wrapping the Qpid C++ library using SWIG >> (just as the python and ruby bindings currently do). So after a lot >> of playing and SWIG-debug work, I now have a (rough) PHP library that >> works :) >> >> Although I still have a fair bit of clean-up to do, it looks like all >> that will be required in the end is a custom SWIG *.i interface file >> for the PHP library, and a couple of minor "#if[n]def SWIGPHP" >> directives in the messaging/Session.h header (to work around some >> SWIG::PHP limitations). And a relevant Makefile.am too I 'spose. >> >> So, my question is, how would you like me to contribute the PHP work >> back to Qpid? I'm perfectly happy to just attach the final files to a >> JIRA issue (would https://issues.apache.org/jira/browse/QPID-2777 be >> appropriate? or should I create new JIRA issue specifically for PHP?). >> I'm also just as happy to do an "svn commit" once its ready... >> whatever works best for you guys. >> >> Thanks! :) >> >> Paul Colby >> -- >> http://colby.id.au >> >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:dev-subscr...@qpid.apache.org >> >> > > > -- > Regards, > > Rajith Attapattu > Red Hat > http://rajith.2rlabs.com/ > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
