On Fri, Jul 10, 2026 at 1:06 AM C.J. Collier <[email protected]> wrote:
> > It would give modern cloud-native drivers a standard interface to target, > rather than everyone hacking their own custom event loops into individual > DBDs. > > Thoughts? > Nice! The problem with event loops is that a system should have only one. Is there a thing like "async-check-and-do" that will do stuff or not block, that could get polled as part of an existing event loop? A quick search yields https://metacpan.org/dist/POE-Component-EasyDBI for discussion; POE wants to be the standard event loop services provider. I'm old-school and still write loops around select(2), which allows async comms with separate processes using a little language over a pipe, robustly, but that's no way to define a standard interface unless the facility gets wrapped somehow. The tradeoff of only polling after the select times out would be acceptable, I think, although it wouldn't be as responsive as including the protobuf system's file descriptors in the select set. I don't know if there is a standard for mapping a FD number to a [on-readable, on-writable, on-error] coderef triple, aside from just doing that with an AoA, but were I wanting to integrate an async system into an existing select loop, I could work with that. Especially if the system offered to take the same shape of data as an input for its own select loop.POE might have a standard for such things, I don't know. cheers dln -- "The profit motive is often in conflict with the aims of art." -- Ursula K. Le Guin
