Feature request: add systemd support to ListenAndServe about dns HOT 6 CLOSED

Obviously this needs a new starting point next to ListenAndServe, maybe StartAndService?

from dns.

Proof of concept implemented in the systemd branch

from dns.

I've taken a look at systemd branch. A couple of comments:

• there's not much point accepting a slice of each, then only taking the first element. Just take a single instance to begin with and check for non-nil
• possibly better to have UDP taking precedence over TCP

from dns.

I was wondering about this too. When does systemd give you multiple
sockets? And is it possible to get UDP and TCP sockets at the same time?
On 19 Jul 2014 00:36, "Ian Bishop" [email protected] wrote:

I've taken a look at systemd branch. A couple of comments:

• there's not much point accepting a slice of each, then only taking
  the first element. Just take a single instance to begin with and check for
  non-nil
• possibly better to have UDP taking precedence over TCP

—
Reply to this email directly or view it on GitHub
#100 (comment).

from dns.

Yes, you can have multiple UDP and TCP sockets being returned. A systemd.socket config file might look like this for example:

ListenStream=192.168.1.1:53
ListenStream=10.0.0.1:53
ListenDatagram=192.168.1.1:53
ListenDatagram=10.0.0.1:53

Where ListenStream corresponds to TCP and ListenDatagram corresponds to UDP.

from dns.

Ah OK. Those are then all send. Then the current code in server.go does not
work. There, the serveUDP/TCP need to be started in goroutines. Bit then we
also need to think about the return value of that function.
On 19 Jul 2014 08:31, "Ian Bishop" [email protected] wrote:

Yes, you can have multiple UDP and TCP sockets being returned. A
systemd.socket config file might look like this for example:

ListenStream=192.168.1.1:53ListenStream=10.0.0.1:53ListenDatagram=192.168.1.1:53ListenDatagram=10.0.0.1:53

Where ListenStream corresponds to TCP and ListenDatagram corresponds to
UDP.

—
Reply to this email directly or view it on GitHub
#100 (comment).

from dns.