- From: Gary Brown <gary@pi4tech.com>
- Date: Fri, 21 Jul 2006 09:30:44 +0100
- To: "Monica J. Martin" <Monica.Martin@Sun.COM>
- CC: 'WS-Choreography List' <public-ws-chor@w3.org>
The only side effect from enabling recursion is the usual one - if there is no way to break out of it, then at some point the service will fail with a stack overflow. However, although the consequences may not be as drastic, a similar problem may occur when using repetition, if the conditions are not correctly specified, then the service may never break out of the repetition. Regards Gary Monica J. Martin wrote: > >> brown: Although repetition can be used in some cases to simulate >> recursion, this is not always the case, and it makes the choreography >> complicated. So would suggest removing this restriction to enable >> recursive interaction patterns to be specified. >> >> 6.3 Composing Choreographies >> Second set of bullet points, remove >> >> "There MUST NOT be a cyclic dependency on the choreographies >> performed. For example, choreography "C1" is performing choreography >> "C2" which is performing choreography "C1" again is disallowed" > > mm1: What side effects could we potentially see if we lift this > restriction? (race conditions for example) Thanks. > > > > >
Received on Friday, 21 July 2006 08:30:57 UTC