Are there standardized responses for UNIX socket connections? For example, `OK\n` or `ERROR\n` for unknown commands? Or is it totally up to the implementation?
I love how simple UNIX sockets are! All you have to do is add a listener to a file handle and send random bytes as data to the socket file, e.g. via `echo "hello world" | socat - UNIX-CONNECT:/tmp/myproject1000/mysocket.sock`.
Playing around with it is so much fun 
I tried implementing a UNIX socket handler (L58) in Go 
in the following file. Would you consider this OK, valid, or correct?
The `.sock` file is cleaned up on `ctx.Done()`. I kind of achieved my goal. I have to add a pre-cleanup in case of an ungraceful shutdown. However, in case of a canceled context, it works right now
@deavmi #UnixSocket is more performant but you will need to use a proxy container. If you're interested how I made it work, check my github page.
https://github.com/madnuttah/unbound-docker/blob/main/doc/DETAILS.md#cachedb-redis
#redis, #pihole and #unbound. The holy trinity.
Oops, there's a code block off I see.
Nice article on Understanding Unix Domain Sockets in Golang by @douglasmakey
https://dev.to/douglasmakey/understanding-unix-domain-sockets-in-golang-32n8
#unix #linux #golang #SocketProgramming #GolangTutorials #golangtips #UnixSocket
Lukas Rotermund (moved)
N-gated Hacker News
ϺΛDИVTTΛH
Astra Kernel 
あいじす💫Ma自鯖