| 2010-06-04 06:25:48 utc | jmettraux | tosch_le : many thanks for your email |
| 2010-06-04 06:27:32 utc | tosch_le | never mind. as it was about ruote-jig, i've got a natural interest... |
| 2010-06-04 06:28:10 utc | jmettraux | I won't make it for today with ruote 2.1.10 :( |
| 2010-06-04 06:28:15 utc | tosch_le | apropos ruote-jig: it's not that ruote 2.1ish as it deals a lot with blocks :( |
| 2010-06-04 06:28:25 utc | jmettraux | ouch |
| 2010-06-04 06:28:33 utc | tosch_le | never mind, /participants have to wait, too |
| 2010-06-04 06:29:14 utc | jmettraux | busy ? |
| 2010-06-04 06:29:27 utc | tosch_le | you can use ruote-jig without blocks, but it's much more flexible if you use them. |
| 2010-06-04 06:29:45 utc | tosch_le | yeah, quite a bit. |
| 2010-06-04 06:29:49 utc | jmettraux | what do you mean by blocks ? |
| 2010-06-04 06:29:54 utc | tosch_le | ruby blocks |
| 2010-06-04 06:30:13 utc | tosch_le | procs to be more precise |
| 2010-06-04 06:30:25 utc | jmettraux | that can't be serialized I guess |
| 2010-06-04 06:30:38 utc | tosch_le | yessss... |
| 2010-06-04 06:32:11 utc | jmettraux | the balance between using ruote-jig and writing a custom participant |
| 2010-06-04 06:32:51 utc | tosch_le | but anyway, if someone has to customize the way his http requests are generated, he has tp write a custom participant |
| 2010-06-04 06:33:00 utc | tosch_le | oh, you were faster... |
| 2010-06-04 06:33:05 utc | jmettraux | ;-) |