Re: Connect to Unix domain socket instead of host:port

[Gary E. Miller]

Yo Andreas!

On Thu, 19 Dec 2024 23:43:35 +0100
Andreas B <panden@gmail.com> wrote:

> One of the reasons I want to use a Unix domain socket exclusively, is
> to not expose anything to the network.

Simple, just do not use -G.  Now nothing exposed on the etwork.

> If all clients are local, I thought that this was an example of doing
> things 'the smart way'.

I call it "the hard way', but UNIX is choice.  You want to make more work
for yourself, go ahead.

> If I'm not going to use TCP, why expose it?

Which is why that is the default.

> But there's no efficiency argument, you say? There is no network stack
> involved; wouldn't that increase efficiency a little tiny bit?

The overhead in the packetizer is more than all other overhead combined.
Nothing else is more than a blip.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        gem@rellim.com  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin