This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html
As tasks appear and disappear, it is sometimes too tedious to perform all the chores for each task. In such cases, we merely difference the new tasks and add them to the list. This prevents the cleanup on each job as they are left. A large-scale global shutdown may suffice later.
If there are multiple registrations that need to be kept in sync, they get harder to maintain. It is easier if the lists can be combined or there is a one-to-one mapping between the lists
Failed tasks may require new tasks to be added in which case, it is better to find the failed tasks as separate from the otherwise new tasks.
When the tasks are constantly replenished, it is helpful to keep track of in versus out.
The tasks that are out are candidates for cleanup.
The tasks that are in are either existing or new. They are mutually exclusive so it is easy to tell the new ones from the old ones.
The tasks that are new will need things set up for them to execute. It involves initialization so that they can be included in the list
No comments:
Post a Comment