public
Fork of kennethkalmer/ruote-amqp
Description: AMQP Participant/Listener pair for ruote
Homepage:
Clone URL: git://github.com/asm/ruote-amqp.git
name age message
file .gitignore Sun Jul 12 23:57:14 -0700 2009 Work for ruote 0.9.21 [kennethkalmer]
file History.txt Loading commit data...
file Manifest.txt Mon Aug 03 06:19:18 -0700 2009 0.9.21.1 - Use persistent messages by default [kennethkalmer]
file PostInstall.txt Sun Jul 12 22:45:16 -0700 2009 Initial commit [kennethkalmer]
file README.rdoc
file Rakefile
file TODO.txt Mon Jul 13 02:30:24 -0700 2009 0.9.21 - Added support for default queues and m... [kennethkalmer]
directory lib/
file ruote-amqp.gemspec Mon Aug 03 06:19:18 -0700 2009 0.9.21.1 - Use persistent messages by default [kennethkalmer]
directory script/ Sun Jul 12 22:45:16 -0700 2009 Initial commit [kennethkalmer]
directory spec/
directory tasks/ Sun Jul 12 22:45:16 -0700 2009 Initial commit [kennethkalmer]
README.rdoc

ruote-amqp

DESCRIPTION:

ruote-amqp provides an AMQP participant/listener pair that allows you to distribute workitems out to AMQP consumers for processing.

To learn more about remote participants in ruote please see openwferu.rubyforge.org/part.html

FEATURES/PROBLEMS:

  • Flexible participant for sending workitems
  • Flexible listener for receiving replies
  • Fully evented (thanks to the amqp gem)

SYNOPSIS:

Please review the detailed RDOC in RuoteAMQP::Participant and Ruote::AMQP::Listener

REQUIREMENTS:

NOTE: It might be required that you build the amqp gem yourself.

ruote 2.0.0 is currently only available to build on your own since John Mettraux is working tirelessly to ship a stable ruote 2.0. To build your own ruote 2.0.0 gem run these commands:

  $ git clone git://github.com/jmettraux/ruote.git
  $ cd ruote
  $ git checkout --track origin/ruote2.0
  $ rake gem
  $ sudo gem install pkg/ruote-2.0.0.gem

Please note that this requires Rubygems 1.3.2 or newer to work

INSTALL:

Please be sure to have read the requirements section above

  • sudo gem install ruote-amqp

TESTS:

To run the tests you need the following requirements met, or the testing environment will fail horribly.

kennethkalmer-amqp

It contains a one-line patch as per tmm1’s instructions in #eventmachine, which allows the reactor to be stopped and started several times in a running Ruby process.

RabbitMQ vhost

The tests use dedicated vhost on a running AMQP broker. To configure RabbitMQ you can run the following commands:

  # rabbitmqctl add_vhost /ruote-test
  # rabbitmqctl add_user ruote ruote
  # rabbitmqctl set_permissions -p /ruote-test ruote '.*' '.*' '.*'

If you need to change the AMQP configuration used by the tests, edit the +spec/spec_helper.rb+ file.

DAEMON-KIT:

Although the RuoteAMQP gem will work perfectly well with any AMQP consumer, it is recommended that you use daemon-kit to write your remote participants.

daemon-kit offers plenty of convenience for remote participants and includes a code generator for ruote remote participants.

DaemonKit doesn’t currently support ruote 2.0, support is forthcoming.

LICENSE:

(The MIT License)

Copyright © 2009 Kenneth Kalmer

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ‘Software’), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED ‘AS IS’, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.