Re: ping
[email protected] ("Kurt Starsinic" via dbi-users) Fri, 10 Jul 2026 12:30:22 -0400
| Newsgroups | perl.dbi.users |
|---|---|
| Message-ID | <[email protected]> |
--2d2055ac5440eba1b2716dbe67e6cfb23daad554 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Poong. I am also here, in the process of reorganizing my mental space to= start putting some regular attention toward DBI. - urt On Fri, Jul 10, 2026, at 03:32, David Nicol wrote: >=20 > On Fri, Jul 10, 2026 at 1:06=E2=80=AFAM C.J. Collier <cjac@colliertech= .org> wrote: >>=20 >> It would give modern cloud-native drivers a standard interface to tar= get, rather than everyone hacking their own custom event loops into indi= vidual DBDs. >>=20 >> Thoughts? >=20 >=20 > Nice! The problem with event loops is that a system should have only o= ne. 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?=20 >=20 > A quick search yields https://metacpan.org/dist/POE-Component-EasyDBI = for discussion; POE wants to be the standard event loop services provide= r. >=20 > I'm old-school and still write loops around select(2), which allows as= ync comms with separate processes using a little language over a pipe, r= obustly, but that's no way to define a standard interface unless the fac= ility gets wrapped somehow. The tradeoff of only polling after the selec= t times out would be acceptable, I think, although it wouldn't be as res= ponsive as including the protobuf system's file descriptors in the selec= t set. >=20 > I don't know if there is a standard for mapping a FD number to a [on-r= eadable, on-writable, on-error] coderef triple, aside from just doing th= at 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 o= ffered to take the same shape of data as an input for its own select loo= p.POE might have a standard for such things, I don't know. >=20 > cheers >=20 > dln >=20 >=20 > -- > "The profit motive is often in conflict with the aims of art." -- Ursu= la K. Le Guin --2d2055ac5440eba1b2716dbe67e6cfb23daad554 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE html><html><head><title></title></head><body><div>Poong. I am = also here, in the process of reorganizing my mental space to start putti= ng some regular attention toward DBI.</div><div><br></div><div>- urt</di= v><div><br></div><div>On Fri, Jul 10, 2026, at 03:32, David Nicol wrote:= </div><blockquote type=3D"cite" id=3D"qt" style=3D""><div dir=3D"ltr"><d= iv dir=3D"ltr"><br></div><div class=3D"qt-gmail_quote qt-gmail_quote_con= tainer"><div dir=3D"ltr" class=3D"qt-gmail_attr">On Fri, Jul 10, 2026 at= 1:06=E2=80=AFAM C.J. Collier <<a href=3D"mailto:[email protected]= ">[email protected]</a>> wrote:</div><blockquote class=3D"qt-gmail= _quote" style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;margi= n-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-c= olor:rgb(204, 204, 204);padding-left:1ex;"><div dir=3D"auto"><div dir=3D= "auto"><div dir=3D"auto"><br></div><div dir=3D"auto">It would give moder= n cloud-native drivers a standard interface to target, rather than every= one hacking their own custom event loops into individual DBDs.</div><div= dir=3D"auto"><br></div><div dir=3D"auto">Thoughts?</div></div></div></b= lockquote></div><div><br></div><div><br></div><div>Nice! The problem wit= h event loops is that a system should have only one. Is there a thing li= ke "async-check-and-do" that will do stuff or not block, that could get = polled as part of an existing event loop? </div><div><br></div><div= >A quick search yields <a href=3D"https://metacpan.org/dist/POE-Com= ponent-EasyDBI">https://metacpan.org/dist/POE-Component-EasyDBI</a> for = discussion; POE wants to be the standard event loop services provider.</= div><div><br></div><div>I'm old-school and still write loops around sele= ct(2), which allows async comms with separate processes using a little l= anguage over a pipe, robustly, but that's no way to define a standard in= terface unless the facility gets wrapped somehow. The tradeoff of only p= olling after the select times out would be acceptable, I think, although= it wouldn't be as responsive as including the protobuf system's file de= scriptors in the select set.</div><div><br></div><div>I don't know if th= ere 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 s= ame shape of data as an input for its own select loop.POE might have a s= tandard for such things, I don't know.</div><div><br></div><div>cheers</= div><div><br></div><div>dln</div><div><br></div><div><br></div><div><spa= n class=3D"qt-gmail_signature_prefix">--</span></div><div dir=3D"ltr" cl= ass=3D"qt-gmail_signature"><div dir=3D"ltr"><span class=3D"font" style=3D= "font-family:"times new roman", serif;">"The profit motive is = often in conflict with the aims of art." -- Ursula K. Le Guin</span></di= v></div></div></blockquote></body></html> --2d2055ac5440eba1b2716dbe67e6cfb23daad554--