SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : The *NEW* Frank Coluccio Technology Forum

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: axial who wrote (421)7/16/2000 4:16:31 AM
From: ftth  Read Replies (2) of 46821
 
Hi Jim, just a little addendum on the CSMA/CD/CA stuff, to sort out the main differences at a high level:

CD doesn't actually avoid collisions; it makes 'em stick out like a sore thumb by broadcasting a jam signal when they are detected so there can be no ambiguity to any station on the LAN that a collision happened. Collisions are a normal part of operation and (barring a massively overprovisioned collision domain or flakey hardware) normal operation continues immediately following the collision.

CD can't really be used in the wireless case, in general, because not every station can "hear" every other station (unlike a LAN collision domain). For example, say station A is on the north side of a building and is transmitting to a base to the north. Say station B is located south and west of station A, sending to the same base. It's quite possible that neither A or B can hear each other. That's just a simple case. Any given station would have to be able to hear every other station in order to be able to unambiguously *detect* any collision (this is not completely true but I'm being general). This is why CA is used, rather than CD (CA essentially is a handshake for a station to claim the channel for a specified period, granted by the base, or receiving station).

There's more to it, but this is the general idea.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext