From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Unix APIs: elegant or not?
Date: Thu, 1 Nov 2018 08:31:25 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.1811010827590.78183@aneurin.horsfall.org> (raw)
In-Reply-To: <CABH=_VQ2U3UvtNSDtmMpfd2Ap9JT4Zbag0qYcN2yYwyYU5_TuQ@mail.gmail.com>
On Wed, 31 Oct 2018, Paul Winalski wrote:
> I've always thought that the UNIX file primitives very elegantly adhere
> to this principle. [...]
Until Berkeley introduced sockets, which has the worst API that I've ever
seen in Unix-land...
Last place I worked, they had a library that simplified it; the
application said "I am a server on port NNN" and the client said "I want
to talk to port NNN on 1.2.3.4" etc.
I wish I'd "borrowed" that code when I left.
-- Dave
next prev parent reply other threads:[~2018-10-31 22:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 4:38 Warren Toomey
2018-10-31 15:47 ` Paul Winalski
2018-10-31 17:22 ` Clem Cole
2018-10-31 19:33 ` Lawrence Stewart
2018-10-31 20:57 ` G. Branden Robinson
2018-10-31 21:31 ` Dave Horsfall [this message]
2018-11-01 7:42 ` Pierre DAVID
2018-11-01 10:20 ` Dave Horsfall
2018-11-01 12:57 ` Clem Cole
2018-11-01 14:19 ` ron minnich
2018-11-01 14:41 ` Clem Cole
2018-11-01 16:43 ` Warner Losh
2018-11-01 16:48 ` ron minnich
2018-11-01 16:56 ` Warner Losh
2018-11-02 5:24 ` Bakul Shah
2018-11-04 10:53 ` Chris Hanson
2018-11-04 15:34 ` ron minnich
2018-11-04 17:06 ` Warner Losh
2018-11-04 20:00 ` ron minnich
2018-11-04 18:52 ` Bakul Shah
2018-11-04 10:49 ` Chris Hanson
2018-11-04 12:28 ` arnold
2018-11-04 21:34 ` Chris Hanson
2018-11-05 14:11 ` Donald ODona
2018-11-04 13:35 ` Warner Losh
2018-11-04 19:47 ` Dave Horsfall
2018-11-01 15:39 Noel Chiappa
2018-11-04 22:29 Theodore Y. Ts'o
2018-11-04 22:37 Noel Chiappa
2018-11-05 4:04 ` Dave Horsfall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.BSF.2.21.9999.1811010827590.78183@aneurin.horsfall.org \
--to=dave@horsfall.org \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).