On 21 Dec 2023, at 08:38, Mario Rugiero <[email protected]> wrote: > > On 21 Dec 2023, at 08:06, Laurent Bercot <[email protected]> wrote: >> * shibari-0.0.1.0 >> --------------- >> >> A brand new project, because I clearly don't have enough on my plate. >> shibari is a suite of DNS tools, a successor to s6-dns. Eventually it >> will fully replace s6-dns, but for now it simply depends on it. This >> first version of shibari comes with two DNS server programs (one for UDP >> and one for TCP), that are more or less drop-in replacements for djb's >> tinydns and axfrdns. (I wrote them because it was a better long-term >> solution than adding a patch to fix a bug in axfrdns.) > > Out of curiosity, is there any reason this is coupled with its own server > rather > than forked from s6-tcpserver and the like? I always found it odd that tinydns > worked differently from most other DJB tools. > Is it some assumption about the load it'll be handling?
Nevermind, I just noticed that seems to be the case only for UDP, but TCP does work by forking from a separate server in shibari. The difference in UDP is that not having a connection makes it harder to model with the stdin/stdout method of UCSPI, right?
