This post originated from an RSS feed registered with Ruby Buzz by Obie Fernandez. Original Post: ActiveMessaging Coming Soon Feed Title: Obie On Rails (Has It Been 9 Years Already?) Feed URL: http://jroller.com/obie/feed/entries/rss Feed Description: Obie Fernandez talks about life as a technologist, mostly as ramblings about software development and consulting. Nowadays it's pretty much all about Ruby and Ruby on Rails. Latest Ruby Buzz Posts Latest Ruby Buzz Posts by Obie Fernandez Latest Posts From Obie On Rails (Has It Been 9 Years Already?)

I'm so excited to talk to people about ActiveMessaging for Ruby on Rails, but it's unreleased so I think I'm not supposed to blog about it yet. Ah, whatever... I'll give you a taste of it anyway. We're using ActiveMessaging on my current project and it is the bom-diggity. No joke, it took us about 6 lines of code to implement distributed worker support in our app.

Myself and others (Chris and Jon primarily, since they wrote it) will be posting more of substance later. In the meantime, here is a silly little infinite loop that Jon posted on our Campfire recently...

class HelloWorldProcessor < ActiveMessaging::Processor
 
 subscribes_to :hello_world
 publishes_to :hello_world
 
 def on_message(message)
   puts "received: " + message.body
   publish :message => "Hello world!"
 end
 
end

And also a bridge.

class BridgeProcessor < ActiveMessaging::Processor
 
 subscribes_to :input
 publishes_to :output
 
 def on_message(message)
   publish :message => message.body
 end
 
end

ActiveMessaging depends on the Ruby bindings for the Stomp protocol and the configuration needed to make it all come together is very, very, minimal. Basically just telling Stomp the hostname of the message broker.

Not bad, eh? There's nothing else published about ActiveMessaging yet -- I won't even tell you how to get it. But if you really, really want to find out more and get your hands on a pre-release copy then try hanging out where the cool AM kids are and you might get hooked up.