3 ms·
Author here. This article is part of series. (1) Creating sockets (2) Addressing soon to come (3) AF_INET6 archeology: scope id and flowinfo (4) bind/conne
by majke 7y ago
Author here. This article is part of series.
(1) Creating sockets
(2) Addressing
soon to come
(3) AF_INET6 archeology: scope id and flowinfo
(4) bind/connect
I'm trying to build an audience, so make sure to follow me on twitter https://twitter.com/majek04 https://twitter.com/majek04
(I don't like harvesting emails, so opted for twitter)
- beefhash 7y agoI've read your post about a brief history select(2) and kind of tried to go down with archaeology as to how the BSD sockets API came to be the way it is (struct sockaddr before struct sockaddr_storage, connect and bind being separate states, read/write v. recv/send), but it's been very hard trying to get complete documentation on the evolution since the first BBN drafts. Food for extra thought I suppose; there's probably a lot of knowledge and trivia to be gleaned from the historical evolution of the interfaces, and I'd imagine you're in a better position to actually sink your fangs into this. Incidentally, your post is time travelling and claims being from Dec 6, 2019.