|WikiProject Computing / Networking||(Rated C-class, High-importance)|
I am proposing to make ATM a subsection under "Packet-based communications", as I think it's useful to compare the general concepts for TDM and packet-based. Each of these would list and link to the corresponding articles: T-1, E-1, SONET, etc. for TDM, and Ethernet, Frame Relay, ATM, X.25, etc. for packet-based. Is this the appropriate article for this?Bert490 04:07, 16 August 2006 (UTC)
- ATM networks has nothing to do with serial communication, which is a physical layer issue. I have removed it as well as TDM.
- Packet mode communication or packet oriented communication is an alternative name to your article. What you suggest is also described in statistical multiplexing, asynchronous communication and packet switched communication. Mange01 21:49, 7 November 2006 (UTC)
There's a page for serial port and one for serial communications. There's one for parallel port, but none for parallel communications, which redirects to parallel port. IMO it would be best to combine the first two and turn one into a redirect, but I'm not sure and I'm not necessarily knowledgeable enough to do it. Any comments? Fpahl 14:51, 14 Sep 2004 (UTC)
- I disagree. Serial communications is much more broad, and doesn't necessarily involve a serial port. Also, many kinds of serial communications ports are not called "serial" ports, but are given more appropriate names like "Ethernet" ports. --Rick Sidwell 2 July 2005 00:20 (UTC)
- I've got to second that disagreement:- Serial Communications are a pretty broad concept, used in all manner of places. On the other hand, a serial port is a computer connector (and associated bits). To draw an analogy, we wouldn't merge USB with serial communications even though USB is a method of serial communications. If anything, parallel communications needs a writeup. Mike1024 (talk/contribs) 23:36, 13 September 2005 (UTC)
Is this an RS232 or a serial communications page? I propose that RS232C stuff be moved to its own page. At least, right before "COMMON BAUD RATES" make a section that delves into RS232.
Frame-based vs. stream-based
Hi. I came here looking for information on frame-based (is this packet-based?) vs. stream-based, and didn't see anything. If I knew anything, I'd write it in, but I don't. —The preceding unsigned comment was added by 22.214.171.124 (talk) 00:22, 8 February 2007 (UTC).
- Yes. Serial transmission is a 2-sentence stub anyway with only a few links to it. --Wtshymanski (talk) 15:38, 11 February 2009 (UTC)
Underlying "physical layer" specification?
Both specifications documents for IEEE1394 and USB call out the same underlying serial communications physical layer but the standards have different packet formatting. Both specifications are not public per se but one can find copies. I would like to reference the physical layer but can't locate my spec sheets right now. Shjacks45 (talk) 16:31, 27 October 2013 (UTC)
The reference to clock skew in serial vs parallel isn't quite right. In fact "bit jitter" is addressed in the USB 3.0 Standard, it is an issue with any synchronous communications over wire. Bit jitter refers to the fact that although electrons travel at "the speed of light" over a wire, the speed at which higher frequency (or more rapidly changing signals) is slower than lower frequency signals. This "velocity factor" is used in designing RF circuitry (e.g. antennas and transmission lines). A Parallel example would be output from a counter: the LSB changes rapidly but the MSB changes slowly, if the data is sync'ed to the counter clock, the MSB data arrives earlier than the LSB signal. Circuit board traces, twisted pairs in cables, act as transmission lines (used as delay lines) also introducing delays. Of course one of the examples of serial (narrow bus) being "better" than parallel is the infamous RAMBUS memory, holding that 16-bit wide memory can be reliably clocked at higher speed than 128-bit wide dual channel RAM. Shjacks45 (talk) 17:05, 27 October 2013 (UTC)