Receive new posts as email.
RSS 0.91 | RSS 2.0
RDF | Atom
Podcast only feed (RSS 2.0 format)
Get an RSS reader
Get a Podcast receiver
Sun | Mon | Tues | Wed | Thurs | Fri | Sat |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | |
7 | 8 | 9 | 10 | 11 | 12 | 13 |
14 | 15 | 16 | 17 | 18 | 19 | 20 |
21 | 22 | 23 | 24 | 25 | 26 | 27 |
28 | 29 | 30 | 31 |
This site operates as an independent editorial operation. Advertising, sponsorships, and other non-editorial materials represent the opinions and messages of their respective origins, and not of the site operator or JiWire, Inc.
Entire site and all contents except otherwise noted © Copyright 2001-2006 by Glenn Fleishman. Some images ©2006 Jupiterimages Corporation. All rights reserved. Please contact us for reprint rights. Linking is, of course, free and encouraged.
Powered by
Movable Type
« Qwest and Time Warner Trial in Denver | Main | BellSouth Launches Service »
This is a pretty poor article in the International Herald Tribune about how mesh networks could help in emergencies like the recent bombs in London: The article defines mesh thus: “it links disparate hot spots into a single, expandable broadband wireless network.” It also says that mesh would have been particularly useful in London because there are lots of hotspots there already. To me, that sounds like mesh would connect a bunch of scattered hotspots that might be far away from each other and might be owned by different people. That’s not at all the case. In fact, the key to mesh is that every hotspot doesn’t require backhaul. Instead, hotspots can pass traffic one to the next until hitting one that connects to the Internet. But mesh doesn’t somehow magically connect different networks or hotspots that are individually owned. Also, like any wireless network, a mesh network could get so congested by users that it can’t carry any more traffic.
Posted by nancyg at August 1, 2005 11:08 AM
Categories: mesh
TrackBack URL for this entry:
https://db.isbn.nu/mt3/mt-tb.pl/3326