From: Paul Ruizendaal via TUHS <tuhs@tuhs.org>
To: Larry McVoy <lm@mcvoy.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Re.: is networking different?
Date: Mon, 4 Jul 2022 23:31:15 +0200 [thread overview]
Message-ID: <D5CB5041-7CEF-4D6E-992E-E44808611DB1@planet.nl> (raw)
In-Reply-To: <20220704204449.GT18597@mcvoy.com>
> On 4 Jul 2022, at 22:44, Larry McVoy <lm@mcvoy.com> wrote:
>
> On Mon, Jul 04, 2022 at 10:09:52PM +0200, Paul Ruizendaal via TUHS wrote:
>> With the above one could do
>>
>> open("/net/inet/org.tuhs.www:80", O_RDWR | O_STREAM)
>>
>> to connect to the TUHS web server, and do
>>
>> open("/net/inet/any:80", O_RDWR | O_STREAM | O_CREAT, 0600)
>>
>> to create a "listening" (rendez-vous) socket.
>
> Decades ago, I tried to make a library that worked like this and it
> was problematic. There are all sorts of setsockopt things that
> you sometimes need to set.
>
> I'd love to be wrong on this, if anyone has a working, for all of the
> normal use cases, library like this, I'd love to see it.
Wouldn’t setsockopt map nicely to ioctl when there is a file system switch? The ioctl would switch into the network stack specific version naturally.
setsockopt(sd, SOL_SOCKET, SO_BROADCAST, &val, sizeof(int))
would become
ioctl(sd, SO_BROADCAST, &val)
More generally, the issue of meta-data and avoiding that ioctl becomes an intractable dumping ground is not easy to solve.
next prev parent reply other threads:[~2022-07-04 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 20:09 [TUHS] " Paul Ruizendaal via TUHS
2022-07-04 20:44 ` [TUHS] " Larry McVoy
2022-07-04 21:31 ` Paul Ruizendaal via TUHS [this message]
2022-07-04 21:33 ` Phil Budne
2022-07-04 21:17 ` ron minnich
2022-07-04 23:37 ` [TUHS] " Paul Ruizendaal
2022-07-05 3:02 ` John Cowan
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=D5CB5041-7CEF-4D6E-992E-E44808611DB1@planet.nl \
--to=tuhs@tuhs.org \
--cc=lm@mcvoy.com \
--cc=pnr@planet.nl \
/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).