ruote tmp/log_2011-03-30.html

2011-03-30 03:55:35 utc biv hi, anyone awake?>
2011-03-30 03:55:36 utc biv \
2011-03-30 07:15:32 utc jmettraux biv: hello
2011-03-30 07:15:40 utc biv hey mate
2011-03-30 07:16:36 utc jmettraux maybe you can place your concurrence / connections logic inside of a participant
2011-03-30 07:16:37 utc biv one sec
2011-03-30 07:16:49 utc biv yeh, will show you what Ive done
2011-03-30 07:20:34 utc biv https://gist.github.com/893996
2011-03-30 07:20:44 utc biv just repairing a broken deployment right now
2011-03-30 07:20:49 utc biv so cant talk, but will be ok to in 20
2011-03-30 07:21:05 utc jmettraux ok
2011-03-30 07:21:48 utc jmettraux I will comment anyway
2011-03-30 07:22:01 utc biv cool
2011-03-30 07:22:03 utc jmettraux looks good
2011-03-30 07:22:47 utc jmettraux maybe use a [custom] class for the participant, so that you can implement a "cancel" behaviour when the whole (or part) of the workflow containing the 'active' participant gets cancelled
2011-03-30 07:24:31 utc biv yup cool
2011-03-30 07:25:22 utc biv (sorry, still on this deployment)