This content has been marked as final. Show 2 replies
When Fork generates the new ChildToken ,then kill the ParentToken?
And create a new 'parent' token when the join has to be left? Don't you have synchronization issues then if multiple child tokens signal the (non existing?) token to continue? and what if the parent token was no root token then you have to keep track of that parents parent token with probably some identical issues....
If it was that simple, I guess the core developers would already have thought about that. but that's just my idea
Don't you have synchronization issues then if multiple child tokens signal the (non existing?) token to continue?
This can set a counter to record the number of the coming child tokens in Join. If the coming tokens' number is equal the into Join Transitions' number, then goes on and creates a new Token.(It refers the Petrin-Net's Token , if place has the enough token then signal the transiton)