[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ebxml-bp] fork/join
David,
For a moment there you had me concerned! I
guess we need to all agree on what
each of these terms means - fork to me means
something totally different.
What you are calling fork - I call 'switch' and
then processing picks a path based
on context (see BPEL example attached) - where the
switch is a side-branch -
relative to the flow diagram you have - so its very
clear that processing is
still occuring within the
overall flow.
Whereas Fork to me means - terminate here and
invoke an external process
non-contiguously, (like someone taking a fork in a road).
Join is not really needed for 'switch', when
you have an implied 'end switch'.
But Join may be needed to jump across to some other path - from
the current
path - this is the equivalent to a classic "goto #anchor", and you then need to
ensure deterministic outcomes - such as
using "terminate()" or "return()".
We could be in danger here of re-inventing
programming 101 of course!!!
DW.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]