20 lines
3.1 KiB
HTML
20 lines
3.1 KiB
HTML
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
|
||
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>bang path</title><link rel="stylesheet" href="../../jargon.css" type="text/css"/><meta name="generator" content="DocBook XSL Stylesheets V1.61.0"/><link rel="home" href="../index.html" title="The Jargon File"/><link rel="up" href="../B.html" title="B"/><link rel="previous" href="bang-on.html" title="bang on"/><link rel="next" href="banner.html" title="banner"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">bang path</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bang-on.html">Prev</a> </td><th width="60%" align="center">B</th><td width="20%" align="right"> <a accesskey="n" href="banner.html">Next</a></td></tr></table><hr/></div><dt><a id="bang-path"/><dt xmlns="" id="bang-path"><b>bang path</b>: <span xmlns="http://www.w3.org/1999/xhtml" class="grammar">n.</span></dt></dt><dd><p> [now historical] An old-style UUCP electronic-mail address
|
||
specifying hops to get from some assumed-reachable location to the
|
||
addressee, so called because each <a href="../H/hop.html"><i class="glossterm">hop</i></a> is signified
|
||
by a <a href="bang.html"><i class="glossterm">bang</i></a> sign. Thus, for example, the path
|
||
<tt class="systemitem">...!bigsite!foovax!barbox!me</tt>
|
||
directs people to route their mail to machine <tt class="systemitem">bigsite</tt> (presumably a well-known location
|
||
accessible to everybody) and from there through the machine <tt class="systemitem">foovax</tt> to the account of user <tt class="systemitem">me</tt> on <tt class="systemitem">barbox</tt>.</p></dd><dd><p>In the bad old days of not so long ago, before autorouting mailers
|
||
and Internet became commonplace, people often published compound bang
|
||
addresses using the { } convention (see <a href="../G/glob.html"><i class="glossterm">glob</i></a>) to
|
||
give paths from <span class="emphasis"><em>several</em></span> big machines, in the hopes
|
||
that one's correspondent might be able to get mail to one of them reliably
|
||
(example: <tt class="systemitem">...!{seismo, ut-sally,
|
||
ihnp4</tt>!rice!beta!gamma!me}). Bang paths of 8 to 10 hops were
|
||
not uncommon. Late-night dial-up UUCP links would cause week-long
|
||
transmission times. Bang paths were often selected by both transmission
|
||
time and reliability, as messages would not infrequently get lost. See
|
||
<a href="../T/the-network.html"><i class="glossterm">the network</i></a> and
|
||
<a href="../S/sitename.html"><i class="glossterm">sitename</i></a>.</p></dd><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bang-on.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="../B.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="banner.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">bang on </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> banner</td></tr></table></div></body></html>
|