From: Dan Stromberg <drsalists@gmail.com>
To: Bakul Shah <bakul@iitbombay.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Sockets vs Streams (was Re: forgotten versions
Date: Fri, 17 Jun 2022 15:52:31 -0700 [thread overview]
Message-ID: <CAGGBd_oCr29FNp2ZQN9zeQs_F9aMLOMhOZxk3wRYth_PazZ4kw@mail.gmail.com> (raw)
In-Reply-To: <A25D6D40-13EB-42AC-BB0D-06C7736E2868@iitbombay.org>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
On Fri, Jun 17, 2022 at 9:24 AM Bakul Shah <bakul@iitbombay.org> wrote:
> On Jun 16, 2022, at 4:44 PM, George Michaelson <ggm@algebras.org> wrote:
> >
> > Sockets (which btw, totally SUCK PUS) were coded into things
> > and even (YECHH) made POSIX and IETF spec status. Streams didn't stand
> > a chance.
>
> The stream abstraction is a nice (c)lean abstraction but it doesn't
> quite work for things like multicast or datagrams in general. Plan9
> doesn't have sockets but the way it deals with UDP is not simple either.
> The complexity is in the protocols themselves. Even at layer 2 (below
> the IP layer) the amount of complexity is mind boggling (though I
> suppose high-speed backbone switches do all this in hardware!).
>
I've heard good things about Streams, but never really had a problem with
Sockets once I realized that send's and recv's don't necessarily have a 1-1
correspondence.
I do think that Sockets need something analogous to stdio though.
And I believe inetd allowed you to do that.
[-- Attachment #2: Type: text/html, Size: 1533 bytes --]
next prev parent reply other threads:[~2022-06-17 22:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 23:06 [TUHS] " Rob Pike
2022-06-16 23:17 ` [TUHS] " Earl Baugh
2022-06-16 23:18 ` George Michaelson
2022-06-16 23:44 ` George Michaelson
2022-06-17 0:10 ` Larry McVoy
2022-06-17 16:23 ` [TUHS] Sockets vs Streams (was " Bakul Shah
2022-06-17 17:43 ` [TUHS] " Paul Winalski
2022-06-17 22:52 ` Dan Stromberg [this message]
2022-06-17 7:20 ` [TUHS] " Diomidis Spinellis
2022-06-17 7:33 ` Rob Pike
2022-06-17 8:34 ` arnold
2022-06-17 10:52 ` arnold
2022-06-18 7:05 ` Angelo Papenhoff
2022-06-19 7:50 ` Rob Pike
2022-06-19 8:17 ` Angelo Papenhoff
2022-06-19 8:53 ` Rob Pike
2022-06-19 9:02 ` Angelo Papenhoff
2022-06-19 9:14 ` arnold
2022-06-19 9:19 ` Angelo Papenhoff
2022-06-19 9:23 ` arnold
2022-06-19 11:37 ` Matthias Bruestle
2022-06-19 14:47 ` Kenneth Goodwin
2022-06-19 16:27 ` Al Kossow
2022-06-19 18:32 ` Theodore Ts'o
2022-06-19 18:38 ` Dan Cross
2022-06-21 23:56 ` Jacob Moody
2022-06-22 0:13 ` Larry McVoy
2022-06-22 0:48 ` Rob Pike
2022-06-22 1:55 ` George Michaelson
2022-06-22 2:10 ` Bakul Shah
2022-06-22 2:14 ` Jon Steinhart
2022-06-22 2:19 ` Andrew Hume
2022-06-22 2:58 ` Rob Pike
2022-06-22 3:09 ` George Michaelson
2022-06-22 2:16 ` Andrew Hume
2022-06-22 2:55 ` Brad Spencer
2022-06-17 18:54 [TUHS] Re: Sockets vs Streams (was " Norman Wilson
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=CAGGBd_oCr29FNp2ZQN9zeQs_F9aMLOMhOZxk3wRYth_PazZ4kw@mail.gmail.com \
--to=drsalists@gmail.com \
--cc=bakul@iitbombay.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).