Slashdot Mirror


Using IR Lasers Instead of Fiber

Artifice_Eternity writes: "Can't deal with the trouble, time or expense of digging up the street to get fiberoptic cable to your building in the big city? There's another way...infrared line-of-sight infrared lasers between your building and another one nearby. Repeaters and redundancy can keep the chain going reliably for miles, with gigabit data transmission rates."

5 of 206 comments (clear)

  1. Re:Dr. Evil by AragornSonOfArathorn · · Score: 0, Offtopic

    Dude, I think its past your bedtime... go to bed

    --
    sudo eat my shorts
  2. Re:Wireless networks. by DarkZero · · Score: 1, Offtopic

    Oh my God! These things attract LIGHTNING? Well, I guess that just makes them completely unusable, then. It's too bad... if only we had some sort of device that could protect (lightning) things from lightning (rod)...

  3. Re:infrared? by showboat · · Score: 0, Offtopic

    Like yours is?

  4. Re:Not so funny ... by LoseNotLooseGuy · · Score: 1, Offtopic

    But they where very happy when they got a copper link, since they could count on loosing net connection when there was fog.

    I find it unlikely that these students would go around "letting loose or releasing" their net connection just because of some benign weather phenomenon. On the other hand, I suppose fog could cause the students to fail to retain an IR link. The word you were looking for is losing.

    Congratulations! You have been participant #28 in my campaign to rid Slashdot of this error.

    --
    Proudly correcting Slashdot's most irritating linguistic error since 2002.
  5. Re:And...? by LoseNotLooseGuy · · Score: 1, Offtopic

    So you would loose connection in storms etc.

    I doubt that one would consider "letting loose or releasing" a net connection in the event of a storm, unless there were danger of lightning strikes near conducting cable. However, one might fail to retain connectivity of an IR link in a storm. The word you were looking for is lose.

    Congratulations! You have been participant #29 in my campaign to rid Slashdot of this error.

    --
    Proudly correcting Slashdot's most irritating linguistic error since 2002.