Commentary

Stephen Wellman
 

High-Performance Wireless LAN Is Key To Business Mobility

There has been a lot of talk about improving the performance of the wireless LAN here at this year's Interop. Why do IT departments need high-performance Wi-Fi? Without it, initiatives like business mobility and unified communications will go nowhere fast.

There has been a lot of talk about improving the performance of the wireless LAN here at this year's Interop. Why do IT departments need high-performance Wi-Fi? Without it, initiatives like business mobility and unified communications will go nowhere fast.All this talk about voice over Wi-Fi and dual-mode access is cool, but if the campus Wi-Fi system is some legacy 802.11b deployment, it just ain't gonna work. And most Wi-Fi systems today were state of the art in 2002, but far from that today.

In order to accommodate next-generation access, two things are really needed. The first is more bandwidth, which 802.11n supposedly will solve. If it ever, you know, actually makes it to market.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The second is improved WLAN management. Simply put, if IT managers expect to run voice, video, collaboration, and other high-demand applications on their Wi-Fi networks, those networks are going to need to be every bit as efficient as their wireline systems. We're much closer to this reality today than we were even two years ago, but we're still a ways off. The fact that there are Wi-Fi networking startups still competing with Cisco after all these years is evidence that the WLAN management and performance nut has not yet been fully cracked.

The hard truth about this is that we're still waiting for 802.11n after four years of promise and hype. And we're still waiting for the perfect WLAN system, too.

Does this mean that dual-mode access and business mobility are destined to flop? What do you think?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links