You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present, the activation thread decrements the notification counter immediately after having detected it to be greater than zero and just before executing the Activation Procedure. It might make sense to move the decrement after the Activation Procedure. This would have the advantage that, in the "normal" case where notification are processed one at a time, the notification counter remains different from zero for as long as the Activation Procedure has not finished running. Users can therefore check the value of the Notification Counter if they wish to know whether the processing of the notification is still under way.
The text was updated successfully, but these errors were encountered:
After discussion, it is decided not to implement this change (we would gain in visibility over the completion of the task assigned to the notified task but we would lose in visibility over the status of the notification).
At present, the activation thread decrements the notification counter immediately after having detected it to be greater than zero and just before executing the Activation Procedure. It might make sense to move the decrement after the Activation Procedure. This would have the advantage that, in the "normal" case where notification are processed one at a time, the notification counter remains different from zero for as long as the Activation Procedure has not finished running. Users can therefore check the value of the Notification Counter if they wish to know whether the processing of the notification is still under way.
The text was updated successfully, but these errors were encountered: