1. 802.11n solves all things wireless. Nope. 802.11n remains highly susceptible to degrading performance at a distance.
2. 802.11n will offer 100 Mbps and more everywhere all the time. We wish. 802.11nï¿¼s performance degradation means these performance levels will be achieved SOME of the time, not all the time.
3. Interference is not an issue with 802.11n. 802.11n solves the Wi-Fi speed, but not reliability, so interference is still an issue.
4. 802.11n will eclipse 802.11g for client use. Sure, eventually. But there are still a lot of legacy systems out there, and they wonï¿¼t go away any time soon.
5. The raw capacity of 802.11n makes multimedia support over Wi-Fi a non-issue. Baloney. With applications like voice and video, it's not about bandwidth capacity, it's about delay, and 802.11n alone is not the answer there.
Given these realities, when and where should 802.11n first be deployed? According to Ruckus, a prime initial application of 802.11n is as a backhaul wireless technology for aggregating 802.11g client traffic through a meshed wireless network. This approach doesnï¿¼t require a huge investment to get some 802.11 benefits, while continuing to leverage legacy 802.11g systems and clients. Personally, though, Iï¿¼d push on ahead and convert as many access points and client systems as quickly as you can afford. You simply canï¿¼t have too much bandwidth, and Iï¿¼m convinced that faster connections almost always pay for themselves in productivity gains. Iï¿¼ve already converted my home router, for example, even though several of my machines still use 802.11g, or even 802.11b. I mean, who wants to wait?