From: Stuart Remphrey <stu@remphrey.net>
To: Richard Salz <rich.salz@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Research Datakit notes
Date: Wed, 29 Jun 2022 14:07:11 +0800 [thread overview]
Message-ID: <CAD0_1ckM=c3cexwxC2w2syeaOZ-v810CQig8N5i9tnoy4npM4Q@mail.gmail.com> (raw)
In-Reply-To: <CAFH29tpSfG6dAuvo_rQo9kc9kYv3KkCm70WjPtDEmtyaWUkwEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
Yes, I'd thought of Sun's Jini here, part of their Java push -- which IIRC
exposed network (un)reliability and tried to address it through service
lookup and limited-lifetime lease/renew for remote resource access.
Though I'm not sure it went anywhere?
(or how TUHS-relevant this is/was... apologies if not)
-----
Hmm, apparently Jini became Apache River; last release in 2016, then
retired Feb 2022:
https://en.wikipedia.org/wiki/Jini
On Wed, 29 Jun 2022, 05:36 Richard Salz, <rich.salz@gmail.com> wrote:
> > My theory is that networking is different because it breaks all the time.
>
> This Sun research paper from 1994
> https://scholar.harvard.edu/waldo/publications/note-distributed-computing
> is a classic.
>
>
>
[-- Attachment #2: Type: text/html, Size: 1490 bytes --]
next prev parent reply other threads:[~2022-06-29 6:09 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 23:01 [TUHS] " Paul Ruizendaal
2022-06-25 23:09 ` [TUHS] " Larry McVoy
2022-06-25 23:57 ` Rob Pike
2022-06-26 1:17 ` Paul Ruizendaal
2022-07-02 2:51 ` Grant Taylor via TUHS
2022-07-02 2:57 ` Larry McVoy
2022-06-28 10:38 ` Derek Fawcus
2022-06-28 12:36 ` Rob Pike
2022-06-28 12:45 ` Rob Pike
2022-06-28 13:33 ` Dan Cross
2022-06-28 21:19 ` Lawrence Stewart
2022-06-28 21:34 ` Richard Salz
2022-06-29 6:07 ` Stuart Remphrey [this message]
2022-06-28 16:11 ` Tom Teixeira
2022-06-28 18:28 ` John Floren
2022-06-28 12:47 ` Rich Morin
2022-06-28 13:13 ` Marc Donner
2022-06-28 14:41 ` Clem Cole
2022-06-28 15:54 ` Tom Teixeira
2022-06-28 17:05 ` Adam Thornton
2022-06-28 17:43 ` John Labovitz
2022-06-28 22:45 ` [TUHS] HTTP (was Re: Re: Research Datakit notes) Derek Fawcus
2022-06-26 1:41 ` [TUHS] Re: Research Datakit notes Anthony Martin
2022-06-26 9:52 ` Ralph Corderoy
2022-06-26 11:04 ` Paul Ruizendaal
2022-06-29 20:21 ` Paul Ruizendaal
2022-06-26 2:19 Noel Chiappa
2022-06-26 9:46 ` steve jenkin
2022-06-26 20:35 ` Erik Fair
2022-06-26 21:53 ` Steve Jenkin
2022-06-26 10:16 ` Paul Ruizendaal via TUHS
2022-06-26 13:07 ` John Cowan
2022-06-26 13:35 ` Larry McVoy
2022-06-26 13:58 ` John Cowan
2022-06-27 0:43 Noel Chiappa
2022-06-27 3:00 ` Erik Fair
2022-06-27 21:40 Noel Chiappa
2022-06-27 22:40 ` George Michaelson
2022-06-28 15:50 Noel Chiappa
2022-06-28 21:32 ` Lawrence Stewart
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='CAD0_1ckM=c3cexwxC2w2syeaOZ-v810CQig8N5i9tnoy4npM4Q@mail.gmail.com' \
--to=stu@remphrey.net \
--cc=rich.salz@gmail.com \
--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).