Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!SUVM!POSTMASTER From: POSTMASTER@SUVM.BITNET (Undetermined origin c/o Postmaster) Newsgroups: bit.listserv.novell Subject: (no subject given) Message-ID: Date: 13 Feb 90 23:42:20 GMT Sender: Novell LAN Interest Group Reply-To: Novell LAN Interest Group Lines: 14 Approved: NETNEWS@PSUVM.BITNET Gateway Comments: W: Invalid RFC822 field -- "0 VIA MS.5.6.ACMETONIA.ANDREW.CMU.EDU.PMAX_30; TUE, 13 FEB 90 12:". Rest of header flushed. Comments: E: "From:"/"Sender:" field is missing. This knowlege is not all that you requested nor is it novell specific but here is what I know. Ethernet is good it is widely supported and has a throughput of about 10mbits. Tokenring only puts through 4mbits (except the new 16mbit tokenring) this rooks really good on paper but it doesn't stand up in real life. Ethernet can only get that kind of troughput when there are ideal conditions (only two computers both listening and both recieving) in practice it has a problem that we call wedging. As the load get's greater it tends to peter out because of packet conflicts and the like. Tokenring doesn't have this problem because inherant in the technology is a technique to force packets not to collide. In practice we at CMU athough most of the campus is ethernet get better performance out of tokenring. -ben