@[email protected] doesn't change my confusion about why you would need a queue for this. I just don't understand. Probably just really spoiled Go's fire and forget model
Posts
-
kitsunes.club is playing that old game... 99,999 inbound jobs on the queue, 99,999 inbound jobs.Take one down and process it, 101,203 inbound jobs on the queue.#shitpost #techpost -
kitsunes.club is playing that old game... 99,999 inbound jobs on the queue, 99,999 inbound jobs.Take one down and process it, 101,203 inbound jobs on the queue.#shitpost #techpost@[email protected] wtf even are inbound jobs? Incoming AP events? But why would you need a queue for processing them? Or am I just too spoiled by Go's concurrency model?