From: lm at mcvoy.com (Larry McVoy)
Subject: [COFF] [TUHS] OSI stack (Was: Posters)
Date: Thu, 7 Feb 2019 10:50:54 -0800 [thread overview]
Message-ID: <20190207185054.GA20698@mcvoy.com> (raw)
In-Reply-To: <0572e855-9aac-337f-4f1b-66dda3839e14@spamtrap.tnetconsulting.net>
On Thu, Feb 07, 2019 at 11:07:27AM -0700, Grant Taylor via TUHS wrote:
> On 02/06/2019 01:47 PM, Kevin Bowling wrote:
> >There were protocols that fit better in the era like DeltaT with a simpler
> >state machine and connection handling.?? Then there was a mad dash of
> >protocol development in the mid to late ???80s that were measured by
> >various metrics to outperform TCP in practical and theoretical space.??
> >Some of these seemed quite nice like XTP and are still in use in niche
> >defense applications.
>
> $ReadingList++
Greg Chesson was the guy behind XTP. I worked for him at SGI, he was a
hoot (lost him to cancer a while back). I think I've posted this before
but here he is not long before he died (he came up to bitch about kids
these days with their shiney frameworks and new fangled languages, what's
wrong with C?)
http://mcvoy.com/lm/xtp+excavator
He was an engineer to the core, he refused to take any info from me on how
to run the machine, just sat there and figured it out.
--lm
next prev parent reply other threads:[~2019-02-07 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190206174913.E518318C07B@mercury.lcs.mit.edu>
[not found] ` <CAK7dMtBuLv+62LKknOKAYxCBwLBF2zBJ8TLTXAqnHGekGgAPFA@mail.gmail.com>
2019-02-07 18:07 ` gtaylor
2019-02-07 18:22 ` akosela
2019-02-07 18:33 ` crossd
2019-02-13 3:20 ` dave
2019-02-07 18:50 ` lm [this message]
2019-02-07 19:28 ` [COFF] OSI stack
2019-02-08 2:41 ` gtaylor
[not found] ` <CAK7dMtBQgfNsXnzV_gdQ8BxdiRv__AmBp-LGQMTEOvyNSyKkAA@mail.gmail.com>
2019-02-08 3:43 ` [COFF] [TUHS] OSI stack (Was: Posters) gtaylor
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=20190207185054.GA20698@mcvoy.com \
--to=coff@minnie.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).