| 2010-07-06 01:50:18 utc | jmettraux | dhf: welcome on #ruote |
| 2010-07-06 01:51:31 utc | dhf | Thanks. I did try the ruote-kit as a gem and not source and it worked. Doing it from source does not. |
| 2010-07-06 01:52:07 utc | jmettraux | too bad, I've seen your email |
| 2010-07-06 01:54:25 utc | dhf | jmettraux:What is the time most people including you? I plan on using ruote in an advance healthcare application and I am sure I will have questions. Initial version the engine will be embedded in the app. Then plan to externalize it. Also looking for graphic tools to help the mid user create workflows. |
| 2010-07-06 01:55:09 utc | jmettraux | I'm here during GMT+9 office hours |
| 2010-07-06 01:55:22 utc | dhf | Finally, thanks for the presentation you did remote at railsconf It got me thinking about using ruote for the application. |
| 2010-07-06 01:56:05 utc | jmettraux | posting to the mailing list is better for getting asynchronous help |
| 2010-07-06 01:56:46 utc | dhf | I will use the mailing list. I appreciated your fast response yesterday. |
| 2010-07-06 01:56:56 utc | jmettraux | great |
| 2010-07-06 08:07:12 utc | anb_ | Hello |
| 2010-07-06 08:07:31 utc | jmettraux | anb_: hello |
| 2010-07-06 08:07:48 utc | anb_ | how are you ? |
| 2010-07-06 08:07:56 utc | lbt | hi all |
| 2010-07-06 08:07:58 utc | jmettraux | doing fine, how about you ? |
| 2010-07-06 08:08:02 utc | jmettraux | lbt: hi ! |
| 2010-07-06 08:08:09 utc | anb_ | good, thanks |
| 2010-07-06 08:22:37 utc | anb_ | Anyone knows how to get rid of the "Sinatra::RespondTo::UnhandledFormat: Sinatra::RespondTo::UnhandledFormat" error messages in ruote-kit log ? |
| 2010-07-06 08:22:56 utc | anb_ | or is it just me getting those entries in the log ? |
| 2010-07-06 08:23:16 utc | jmettraux | that one http://groups.google.com/group/openwferu-users/browse_thread/thread/e815a71fe83027df ? |
| 2010-07-06 08:23:43 utc | jmettraux | I'd love to help on that one, but no one gives me steps to reproduce or a stack trace :( |
| 2010-07-06 08:25:31 utc | jmettraux | I have to escape in five minutes |
| 2010-07-06 08:25:44 utc | jmettraux | please post any info on the mailing list |
| 2010-07-06 08:25:58 utc | anb_ | will do, thanks |
| 2010-07-06 08:27:30 utc | jmettraux | ttyl ! |
| 2010-07-06 13:42:52 utc | jmettraux | anb_: no need to answer my email, I could figure it out |
| 2010-07-06 13:43:48 utc | anb_ | ok :) |
| 2010-07-06 13:43:51 utc | anb_ | was git |
| 2010-07-06 14:05:03 utc | jmettraux | anb_: pushed two fixes to http://github.com/jmettraux/ruote-kit |
| 2010-07-06 14:05:09 utc | jmettraux | now replying per email |
| 2010-07-06 14:13:54 utc | anb_ | great |
| 2010-07-06 14:31:09 utc | jmettraux | have a good evening, escaping... |
| 2010-07-07 00:06:41 utc | dhf | when you start an engine, doe it start in it's own thread, or the main thread? |
| 2010-07-07 00:07:41 utc | jmettraux | dhf: hello |
| 2010-07-07 00:08:09 utc | jmettraux | if your wrap a worker within the engine, the engine will let the worker run in its own thread |
| 2010-07-07 00:18:35 utc | dhf | is there a sample of that anywhere? I do not think I have seen that approach yet |
| 2010-07-07 00:24:10 utc | dhf | Also, when a participant is running for any length, is the process dehydrated? I assume a worker runs a participant and does it wait for a reply before going on to the next? |
| 2010-07-07 00:31:46 utc | jmettraux | sample : hold on |
| 2010-07-07 00:32:02 utc | jmettraux | dehydration : happens all the time, piece by piece |
| 2010-07-07 00:33:25 utc | jmettraux | dhf : http://github.com/jmettraux/ruote/blob/ruote2.1/examples/ruote_quickstart.rb#L9-13 |
| 2010-07-07 00:33:37 utc | jmettraux | engine + worker + fs_storage |
| 2010-07-07 00:34:11 utc | jmettraux | when a worker is wrapped within an engine, the engine takes care of letting the work start and run in a dedicated thread (not the main thread) |
| 2010-07-07 00:38:28 utc | dhf | in the application that houses the engine, I will be launching processes all the time based upon input coming from a beanstalkd queue. There is considerable processing prior to starting the selected process. I need to launch the process and forget about it. Going on to handle the next queued item. For first pass I want the simplest approach to get going. Then as I learn more I will externalize the engine. Is this a good approach. |
| 2010-07-07 00:39:03 utc | jmettraux | I think so |
| 2010-07-07 00:39:15 utc | jmettraux | it's only ruby code, nothing engraved in marble |
| 2010-07-07 00:40:10 utc | dhf | that is what I like. It is only ruby code :) |
| 2010-07-07 00:40:39 utc | jmettraux | :) |