I think it is a bug to add workers to the list of available workers for every kind of network activity a queue/broker notices from them. And I'd say this is wrong by design.
Imagine a worker which is currently idle and sending heartbeat messages periodically: The implementation will add this worker over and over again to the list of available workers. The list would grow endlessly if there wasn't expiration management which removes older duplicates continously from the list.
Samples/src/Pirate Pattern/Paranoid Pirate/ParanoidPirate.Queue/Program.cs
Line 77 in 378dad9
I think it is a bug to add workers to the list of available workers for every kind of network activity a queue/broker notices from them. And I'd say this is wrong by design.
Imagine a worker which is currently idle and sending heartbeat messages periodically: The implementation will add this worker over and over again to the list of available workers. The list would grow endlessly if there wasn't expiration management which removes older duplicates continously from the list.