Atlas48/JargonFile
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Original files version 4.4.7

Browse Source
This commit is contained in:
Bob Mottram
2014-03-27 18:54:56 +00:00
parent c632ed8d67
commit cb847ea893
2578 changed files with 26300 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
original/html/N/network-meltdown.html Normal file
View File

@@ -0,0 +1,13 @@
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>network meltdown</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="../N.html" title="N"/><link rel="previous" href="network-address.html" title="network address"/><link rel="next" href="New-Jersey.html" title="New Jersey"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">network meltdown</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="network-address.html">Prev</a> </td><th width="60%" align="center">N</th><td width="20%" align="right"> <a accesskey="n" href="New-Jersey.html">Next</a></td></tr></table><hr/></div><dt><a id="network-meltdown"/><dt xmlns="" id="network-meltdown"><b>network meltdown</b>: <span xmlns="http://www.w3.org/1999/xhtml" class="grammar">n.</span></dt></dt><dd><p> A state of complete network overload; the network equivalent of
<a href="../T/thrash.html"><i class="glossterm">thrash</i></a>ing. This may be induced by a
<a href="../C/Chernobyl-packet.html"><i class="glossterm">Chernobyl packet</i></a>. See also
<a href="../B/broadcast-storm.html"><i class="glossterm">broadcast storm</i></a>, <a href="../K/kamikaze-packet.html"><i class="glossterm">kamikaze packet</i></a>.</p><p>Network meltdown is often a result of network designs that are
optimized for a steady state of moderate load and don't cope well with the
very jagged, bursty usage patterns of the real world. One amusing instance
of this is triggered by the popular and very bloody shoot-'em-up game
<i class="citetitle">Doom</i> on the PC. When used in multiplayer
mode over a network, the game uses broadcast packets to inform other
machines when bullets are fired. This causes problems with weapons like
the chain gun which fire rapidly &#8212; it can blast the network into a
meltdown state just as easily as it shreds opposing monsters.</p></dd><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="network-address.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="../N.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="New-Jersey.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">network address </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> New Jersey</td></tr></table></div></body></html>