# Running asynchronous processes - non-ruby binaries

**URL:** <https://www.ruby-forum.com/t/running-asynchronous-processes-non-ruby-binaries/176107>\
**Category:** Rails\
**Created:** [September 24, 2009, 10:09pm UTC](https://www.ruby-forum.com/t/running-asynchronous-processes-non-ruby-binaries/176107 "2009-09-24T22:09:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![princenamor](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/c0e974/32.png) [@princenamor](https://www.ruby-forum.com/u/princenamor)\
**Post date:** [September 24, 2009, 10:09pm UTC](https://www.ruby-forum.com/t/running-asynchronous-processes-non-ruby-binaries/176107/1 "2009-09-24T22:09:25Z")

</div>

I’m looking at “Advanced Rails Recipes,” and there’s one in here  
called “Process Asynchronous State-Based Workflows.” It seems to  
describe a workflow that is written in Ruby. I have a binary (written  
in C++) which I would like to run with different input files based on  
user input in my Rails application.

My question is:  
Can I still use acts\_as\_state\_machine and simple-daemon? Or do I need  
to modify this recipe?

Many thanks,  
John