# Resque on IronRuby 1.0RC1 (it works) - some feedback

**URL:** <https://www.ruby-forum.com/t/resque-on-ironruby-1-0rc1-it-works-some-feedback/182259>\
**Category:** IronRuby\
**Created:** [January 25, 2010, 6:42pm UTC](https://www.ruby-forum.com/t/resque-on-ironruby-1-0rc1-it-works-some-feedback/182259 "2010-01-25T18:42:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![thbar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/eb8c5e/32.png) [@thbar](https://www.ruby-forum.com/u/thbar)\
**Post date:** [January 25, 2010, 6:42pm UTC](https://www.ruby-forum.com/t/resque-on-ironruby-1-0rc1-it-works-some-feedback/182259/1 "2010-01-25T18:42:09Z")

</div>

Hello,

some feedback from my experiments, in case that’s useful to anyone: I  
wanted  
to see if I could use IronRuby to create Resque workers, and the answer  
looks like yes.

Resque is a nice ruby/Redis-based message queue (introduction here:  
[Introducing Resque - The GitHub Blog](http://github.com/blog/542-introducing-resque)). It comes with a Sinatra  
based UI ([New Resque Web UI - The GitHub Blog](http://github.com/blog/543-new-resque-web-ui)).

I’m using Resque to push XML messages from a Rails internet-based  
back-end  
to IronRuby workers (that will do Excel spreadsheets generation amongst  
other things).

To get this to work, use the edge version of Resque (not the gem 1.3.1),  
and  
tweak IronRuby to tell it doesn’t support Kernel.fork (  
[resque-and-ironruby.rb · GitHub](http://gist.github.com/286052)).

hth,

cheers,

– Thibaut