Kevin Lewis

> Which might be an issue if for instance one topic if DDos-ed with msgs, you can't keep a sererate handler that would be unaffected. 👍 > Hm it's weird...

@dams This doesn't quite work. It leaves orphaned processes for the unsubscribed topic. This can be seen using `:observer`. Looking more closely now.

It looks like the subscribers and workers need to be terminated, so I think this is a bit more complicated.

Yes, `Kaffe.GroupMember` knows all the subscribers and `Kaffe.WorkerManager` has a table of the workers. I'm not sure the supervision tree is optimized for shutting them down, so it might be...

@cristianormd Hello! Glad you're having success with Kaffe! That's an interesting issue. Are you receiving `nil` for `messages` or are you receiving `[nil]`? Looking at this code, I'm guessing the...

@dams This seems like something that's best handled in the consumer and outside of Kaffe. While I can see that there is a measure of convenience in having this maintained...

@dams I think that's basically the mechanics of it, yes. Although I think the `ProcessRegistry` would probably be the new way to do that. If you used the `:via` tuple,...

@dams We're discussing this a bit internally.

I've thought about this a bit more. We would want to maintain backward compatibility by default. I wonder if we could introduce an abstraction somewhere around `Kaffe.Worker`. The default implementation...

That would definitely require some changes to Kaffe. 🤔 We'd be open to a PR on that. Not really even sure how to design it, but the notification might need...