Updates for Jira, Confluence and Bamboo: Tuesday Nov. 14 at 6 pm to Wednesday Nov. 15 (all day)
 
1
0
-1

How should the controller react when a digital press sends a signal that contains Lastrepeat=true and when a system wide subscription was made?

Should the controller then send StopPersistentChannel to close the global Subscription?

The spec in ObservationTarget is a bit dubious but seems to refer to a subscription that was job specific (not a global subscription)

    CommentAdd your comment...

    3 answers

    1.  
      2
      1
      0

      Actually, it's not a good design to mix global subscriptions and specific termination. If you do such a mix, you'll have trouble because of ambiguities.
      Therefore, I think that a LastRepeat should be about the corresponding Subscription. If the subscription is global, the termination is also global.
      If a Digital Press needs to inform that a signal is the last one for a given job because the job is removed, there is the value QueueEntry/@Status="Removed" which implies that there will be no signal for that job anymore.
      I also think that "Removed" should not be sent instead of "Completed" nor "Aborted" but in addition to such states. Else, you the subscriber does not know in which state the job terminates.
      Now, the actual implementations could be different. May be we can clarify this in IDP ICS 1.5, that Bob is starting to edit...

        CommentAdd your comment...
      1.  
        1
        0
        -1

        Rainer, that is correct. In this case there is a global subscription.

        Question is what the controller should do when it receives the LastRepeat=true signal.

        Must is close the subscription then and expected to send a stoppersistent channel? (hoping the DFE still responds?)

          CommentAdd your comment...
        1.  
          1
          0
          -1

          We actually deprecated job-specific subscriptions in JDF 1.5 - see 5.4.6 Scope of Subscriptions

          There is very little added value for a lot of added bookkeeping on the device side + you miss all job-independent events.

            CommentAdd your comment...