From: Paul Ruizendaal <pnr@planet.nl>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Spider
Date: Fri, 24 Jan 2020 02:28:19 +0100 [thread overview]
Message-ID: <EB9601C1-EE17-4E43-B69F-C9802A506597@planet.nl> (raw)
> Ugh. Memory lane has a lot of potholes. This was a really long time ago.
Many thanks for that post - really interesting!
I had to look up "Pierce Network", and found it described in the Bell Journal:
https://ia801903.us.archive.org/31/items/bstj51-6-1133/bstj51-6-1133_text.pdf
In my reading the Spider network is a type of Pierce network.
However, the network that you remember is indeed most likely different from Spider:
- it was coax based, whereas the Spider line was a twisted pair
- there was more than one, whereas Spider only ever had one (operational) loop
Condon and Weller are acknowledged in the report about Spider as having done many of its hardware details. The report discusses learnings from the project and having to tune repeaters is not among them (but another operational issue with its 'line access modules’ is discussed).
All in all, maybe these coax loops were pre-cursors to the Spider network, without a switch on the loop (“C” nodes in the Pierce paper). It makes sense to first try out the electrical and line data protocol before starting work on higher level functions.
I have no idea what a GLANCE G is...
next reply other threads:[~2020-01-24 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 1:28 Paul Ruizendaal [this message]
2020-01-24 2:37 ` Jon Steinhart
2020-01-24 3:03 ` Gregg Levine
2020-01-26 1:01 ` Heinz Lycklama
-- strict thread matches above, loose matches on Subject: below --
2020-01-23 8:38 Paul Ruizendaal
2020-01-23 17:40 ` Jon Steinhart
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=EB9601C1-EE17-4E43-B69F-C9802A506597@planet.nl \
--to=pnr@planet.nl \
--cc=tuhs@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).