| 2012-03-01 07:41:32 utc | tosch_le | jmettraux: https://github.com/tosch/ruote-evented-fs-worker |
| 2012-03-01 07:41:41 utc | tosch_le | good morning! |
| 2012-03-01 07:41:58 utc | jmettraux | tosch_le: good afternoon! Already watching |
| 2012-03-01 07:44:42 utc | jmettraux | I was a bit surprised you had to subclass Ruote::Worker |
| 2012-03-01 07:46:12 utc | hartog | good morning all! |
| 2012-03-01 07:46:27 utc | jmettraux | good afternoon! |
| 2012-03-01 07:46:58 utc | hartog | s/morning/\$localtime/ |
| 2012-03-01 07:49:08 utc | tosch_le | hello hartog |
| 2012-03-01 07:49:37 utc | tosch_le | jmettraux: it's not that i had to, but it saved time and work |
| 2012-03-01 07:50:31 utc | tosch_le | at least that was my idea from the beginning |
| 2012-03-01 07:53:16 utc | jmettraux | I would prefer the worker not to be overriden, it saves time not to have to explain why there is a specific worker |
| 2012-03-01 07:53:25 utc | jmettraux | it's very sexy anyway |
| 2012-03-01 07:54:07 utc | jmettraux | why doesn't wait_for work? |
| 2012-03-01 07:55:42 utc | hartog | hmz... same use case as yesterday (different flavour and colour) and sort of the same solution |
| 2012-03-01 07:56:00 utc | hartog | have a seperate worker / listener |
| 2012-03-01 07:56:48 utc | jmettraux | hartog: it's a ruote worker, not an AMQP worker |
| 2012-03-01 07:57:05 utc | hartog | but it still a seperate worker |
| 2012-03-01 07:58:13 utc | hartog | and it is evented as would be an amqp-listener |
| 2012-03-01 07:59:15 utc | jmettraux | if you use Bunny, you can have a non-evented amqp-listener |
| 2012-03-01 08:00:30 utc | tosch_le | i don't know why wait_for doesn't work. it seems to be some threading issue |
| 2012-03-01 08:01:18 utc | tosch_le | hadn't have the time yet to dig deeper |
| 2012-03-01 08:01:51 utc | hartog | 'evented' not as in EventMachine, but as in : an event occurs; a message arrives |
| 2012-03-01 08:03:15 utc | tosch_le | not having a specialized worker would require a way to stop ruote's worker polling the storage frequently |
| 2012-03-01 08:03:37 utc | tosch_le | i suppose i'm not entirely up to date to your changes during the last months |
| 2012-03-01 08:03:48 utc | jmettraux | tosch_le: you can do this by making get_msgs() blocking |
| 2012-03-01 08:04:55 utc | jmettraux | hartog: ok |
| 2012-03-01 08:14:57 utc | tosch_le | jmettraux: but then i needed to implement my own process method, despite the fact that schedules handling would be complicated, too |
| 2012-03-01 08:19:33 utc | jmettraux | for ruote-swf I had to have specific workers, but they are super light: https://gist.github.com/1948268 they are only here to help differentiating activity workers from decision workers |
| 2012-03-01 08:19:49 utc | jmettraux | all the rest is hidden behind the Ruote::Swf::Storage facade |
| 2012-03-01 08:20:15 utc | jmettraux | the storage hides all the specifics of the backend from the worker[s] |
| 2012-03-01 09:53:59 utc | hartog | btw: I use this for ruote and amqp : https://github.com/wyngle/amqp-hermes |
| 2012-03-01 09:54:41 utc | hartog | (finally got the go sign ;->) |
| 2012-03-01 10:10:38 utc | jmettraux | very nice! |
| 2012-03-01 10:29:57 utc | hartog | thx |