I sure find the getaddrinfo-socket-connect-loop dance rather depressing. It’s a complicated API just to open a connection somewhere, and everyone’s repeating that boilerplate. It would be nice if more systems adapted and eventually standardised on a simpler API, perhaps like dial from plan9:
Totally agreed, it’s a real mess. There are some use cases that aren’t really captured by socket99 yet – In particular, I’m still thinking about the best way to integrate setsockopt(3) use.
I sure find the getaddrinfo-socket-connect-loop dance rather depressing. It’s a complicated API just to open a connection somewhere, and everyone’s repeating that boilerplate. It would be nice if more systems adapted and eventually standardised on a simpler API, perhaps like dial from plan9:
http://man.cat-v.org/9front/2/dial
Totally agreed, it’s a real mess. There are some use cases that aren’t really captured by socket99 yet – In particular, I’m still thinking about the best way to integrate setsockopt(3) use.
I wrote a blog post about the C99 trick that socket99 uses; other old C APIs could benefit from a similar approach.