Dominik Charousset

@dominiklohmann did you test this with asynchronous messages? We do have this code in place: ```c++ auto handle_exception = [&](std::exception_ptr eptr) { auto err = call_handler(exception_handler_, this, eptr); if (x.mid.is_request())...

Is there still something left todo here or can we close this ticket? We have a separate ticket for the Python binding removal / deprecation and the CMake overhaul is...

I've implemented a small micro-benchmark to quantify the performance gain we could gain from switching to the ART (Adaptive Radix Tree). The `filter/extend_...` test adds 100 entries to a filter....

Ok, I've finally sat down with this again. I've started integrating the radix tree when I hit a wall. The implementation made the very unfortunate design decision that the null...

> No real opinion. I don't have hunch how much faster it could be - so would still be interesting to test it if the implementation isn't too involved (assuming...

@awelzel this should be solved since merging #284. Can we go ahead and close this ticket or did you observe another issue since using `deque`?

Would you mind explaining the use case a bit? What kind of Broker-based service would run outside of Zeek but would not allow/want us to use the native peering? At...

> Did I just confuse you because I oversimplified it as `Broker::peer_websocket()`, or are we not even on the same page that this is a use case that needs addressing?...

> To raise `request_message` on the workers, the common pattern I've seen is that on the manager node an explicit re-publish happens. And that pattern is what I'm stamping as...

I do like your `set_idle_handler` idea from https://github.com/actor-framework/actor-framework/discussions/1590#discussioncomment-7218260. But I think there's are two modifiers: strong/weak and repeated/single-shot. What about this idea? ``` // strong ref, called once self->when_idle(1s).once([] {...});...