357
you are viewing a single comment's thread
view the rest of the comments
[-] Scoopta@programming.dev 46 points 3 months ago

Should probably fix that given we've been out of IPv4 for over a decade now and v6 is only becoming more widely deployed

[-] renzev@lemmy.world 28 points 3 months ago

Agreed. Though I wonder if ipv6 will ever displace ipv4 in things like virtual networks (docker, vpn, etc.) where there's no need for a bigger address space

[-] 30p87@feddit.de 5 points 3 months ago

I wish everything would just default to a unix socket in /run, with only nginx managing http and stream reverse sockets.

[-] verstra@programming.dev 4 points 3 months ago

Wait, but if you have, for example an HTTP API and you listen on a unix socket in for incoming requests, this is quite a lot of overhead in parsing HTTP headers. It is not much, but also cannot be the recommended solution on how to do network applications.

[-] WaterWaiver@aussie.zone 1 points 3 months ago

Replacing a TCP socket with a UNIX socket doesn't affect the amount of headers you have to parse.

load more comments (3 replies)
load more comments (9 replies)
this post was submitted on 24 Jun 2024
357 points (96.9% liked)

Programmer Humor

19292 readers
1145 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS