2 Replies Latest reply on Jul 23, 2008 10:04 PM by Liu Peng

    something about Token

    Liu Peng Newbie

      the question extends from the topic
      http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161939#4161939

      Fork generates the childToken from the ParentToken,and the ParentToken always stays in the Fork.
      And the Join cannot have different Fork's Transition into it.

      Why refers to the Petri-Net's Token?
      When Fork generates the new ChildToken ,then kill the ParentToken?

      I just have this idea,but i don't know the feasibility!
      If this can ,i think this will deal with lots of complex synchronizing scenarios

        • 1. Re: something about Token
          Ronald van Kuijk Master

           

          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

          • 2. Re: something about Token
            Liu Peng Newbie

             

            "kukeltje" wrote:
            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)