Hi Alex,
>> However, when I read your explanation, you're interpreting
>> everything in terms of links, sourcing and targeting. What we have
>> here aren't links, we have a signal construct and a join construct.
> Is it fair to say that signal() is like a BPEL <empty> with a target,
> and join() is like an <empty> with a source?
I don't think so:
--cut--
parallel {
put-pizza-in-oven;
pizza-cooked;
signal(diner-ready);
} and {
join(diner-ready, "beer.temperature < 10c");
get-beer-in-fridge;
drink-beer;
}--edn--
The execution path is from pizza-cooked to get-beer-in-fridge and not the
other way round.
In addition, this doesn't solve the problem of different join semantics.
Viele Grüße,
Olly
