OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Fork without Join


Fork without Join

The ebBP standard states (page 64):
The semantics of Fork and Join are such that for instance a Fork MAY be
defined without a corresponding Join. In this case, the TimeToPerform element MUST NOT be used.


If a Fork without Join is specified as an OR-Fork, then such an operation may create multiple threads that are not joined together later on. One of these threads may reach an end state while others are still active. Are the other threads of execution killed then?
An OR-Fork without a Join taken together with Loops may create arbitrary many Threads of control.

Is it simply the responsibility of the designer to avoid such cases (like in many other languages) or is a Fork without Join restricted to only XOR-Forks?

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]