[ 
https://issues.apache.org/jira/browse/QPID-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross closed QPID-1443.
-----------------------------
    Resolution: Won't Do

This 0-10 impl has been superceded by our work in Qpid Proton on an AMQP 1.0 
Ruby binding.

> Merge updated Ruby client
> -------------------------
>
>                 Key: QPID-1443
>                 URL: https://issues.apache.org/jira/browse/QPID-1443
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Ruby Client
>    Affects Versions: M4
>         Environment: Tested with ruby-1.8.6.287-2.fc9.x86_64, should work 
> with older versions of Ruby, too
>            Reporter: David Lutterkort
>         Attachments: ruby-qpid.tar.gz
>
>
> Please replace the existing Ruby client in 
> https://svn.apache.org/repos/asf/incubator/qpid/trunk/qpid/ruby with the 
> updated client at http://people.redhat.com/dlutter/ruby-qpid.tar.gz [1]
> The new client provides full support for AMQP 0.10 and the Qpid management 
> framework. If there is interest, I can also provide  the git repository that  
> was used in the process and contains more details on how the client came 
> about.
> The client is largely a reimplementation of the Python client.
> The sources also contain a Rakefile to ease testing and packaging. To run all 
> tests, run a broker locally and then do 'rake test'
> To package as a rubygem and/or an RPM, run 'rake package' and 'rake rpm'
> This work was done by myself and Ian Main <[email protected]> with a lot of 
> help from Rafael Schloming <[email protected]> and Ted Ross 
> <[email protected]>. Please include them on any communication about merging 
> the client - especially, since I will be on vacation next week ;)
> [1] The detached GPG signature is at 
> http://people.redhat.com/dlutter/ruby-qpid.tar.gz.sig; signing key is 
> FC6E8A22, you can import that with gpg --keyserver keys.gnupg.net --recv-keys 
> FC6E8A22



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to