1002 Ensure every print job removal leads to a notifier

1002 Ensure every print job removal leads to a notifier

In the regular use case when a job is done, it gets removed from the printing providers queue and a notifier is sent out to interested clients about this removal.

If a printing provider de-registers itself (or it crashes), the jobs already in its queue get removed as well, but no notifier is sent out. Waiting clients will wait forever for the job's removal.

Solution

Whenever a printing provider should be removed from the internal database, its queue must be drained first.

Impact

Affected components:

• internal handling for printing provider removal

Backward compatible change:

• yes

API change:

• no

State

Changes available with caps-printing-coordinator-1.1.0