On Mon, 2017-02-13 at 15:06 +0000, Gordon Sim wrote: > On 13/02/17 15:01, Alan Conway wrote: > > On Wed, 2017-02-08 at 11:48 +0000, Gordon Sim wrote: > > > On 07/02/17 20:40, pqvchen1 wrote: > > > > I'm trying to figure out if QPID Messaging API supports AMQP > > > > 1.0 > > > > for ruby? > > > > the document only says it supports multiple language and > > > > version > > > > 1.0, 0-10. > > > > So Not sure if the ruby sample given in this link : > > > > https://qpid.apache.org/releases/qpid-0.32/index.html is for > > > > AMQP > > > > 1.0? > > > > > > The ruby qpid messaging client is a swigged wrapper around the > > > c++ > > > implementation of the API, and the c++ supports 1.0. > > > > > > However, I'm not sure what the state of the ruby binding is at > > > present. > > > I've not really used much and not for a very long time. Trying > > > now I > > > was > > > unable to get the examples to run at all. > > > > > > The .rb files don't seem to get installed, just the .so file. The > > > qpid_messaging.rb file also requires cqpid, whereas the .so is > > > cqpid_ruby. Modifying the qpid_messaging.rb asa qcuik test, I > > > then > > > got > > > unresolved symbol errors. Is there perhaps supposed to be some > > > other > > > component that bridges between these? > > > > > > Anyone else more familiar with how to run the ruby stuff? > > > > It is in need of some love. I am the owner now so that would be my > > job. > > The binding itself is in working shape but the examples, tests and > > installer are in various stages of disrepair, I need to get those > > back > > in order. I'll get to that soon as Ruby and Python are targets for > > simplification to use the C connection_driver with native > > Ruby/Python > > IO, and I will need to get the ruby binding back on track to do > > that. > > Thi is the qpid messaging binding, not the proton one.
Gahh, sorry. No idea about that one. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
