<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0"
 xmlns:blogChannel="http://backend.userland.com/blogChannelModule"
>

<channel>
<title>Topic &#x27;Maybe...&#x27; in forum &#x27;&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Maybe-18504317</link>
<description></description>
<language>en</language>
<pubDate>Sat, 26 Mar 2022 03:42:47 EDT</pubDate>
<lastBuildDate>Sat, 26 Mar 2022 03:42:47 EDT</lastBuildDate>

<item>
<title>Re: Maybe...</title>
<link>http://www.dslreports.com/forum/Re-Maybe-18506011</link>
<description><![CDATA[Time4aNAP posted : <div class="bquote"><SMALL>said by <a href="/profile/295948" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=295948');">ropeguru</a>:</SMALL><BR><BR>Here is a link to what Nextel was testing so you know what I am talking about...And here is an article from the time here on DSLR explaining speeds and the lower latency...</DIV>Is this the full extent of your knowledge of the subject?  You <I>are</I> aware that we're talking about <I>Sprint</I>, not Verizon, right?<br><br>All I see is a single number claim for latency in one (very) limited deployment situation.  What I don't see are numbers for Sprint's EV-DO latency.  How can you claim "lower latency" without making any comparison?<br><br><div class="bquote">While I was referring to Sprint's plans to offer WiMax, of which Sprint's current EV-DO has NOTHING to do with, you had to bring up something irrelavent.</DIV>Let's see...EV-DO is a wireless mobile data service, and WiMAX is a standard for a wireless mobile data service.  Yup, like night and day, they are. :uhh:<br><br><div class="bquote">Additionally you are mixing the three technologies (OFDM, EV-DO, and WiMax) into this post.</DIV>You're accusing <I>me</I> of making you write what you did in your post?  That's the lamest <I>ad hominem</I> attack that I've ever read!<br><br><div class="bquote">While I agree that EV-DO should stay as it is tested and proven, by now, OFDM would have been tested and ether proven or rejected even though WiMax hasn't hardly been looked at.</DIV>I don't understand your obsession with OFDM.  Sure, it works.  It's the modulation scheme of choice for 802.11g and many DSL systems.  But what does that have to do with the price of tea in China?<br><br>So Nextel set up a "WISP the hard way" test in one small market three years ago.  Big deal.  Is this a good reason to abandon a perfectly good network?  Hardly.  Is it a good business move?  Well, they had to <I>give away</I> the service in NC...<br><br>The question is why Sprint should resurrect this project?  Its data rates are no better than those of EV-DO Rev. A.  And unless you consider the big, heavy Nextel handsets an "advantage", there's really nothing compelling about Nextel's old test mule.  Sprint already has EV-DO for now, and, if nobody spoils it first, will have WiMAX for the future.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Maybe-18506011</guid>
<pubDate>Thu, 14 Jun 2007 14:49:46 EDT</pubDate>
</item>
<item>
<title>Re: Maybe...</title>
<link>http://www.dslreports.com/forum/Re-Maybe-18505575</link>
<description><![CDATA[ropeguru posted : Here is a link to what Nextel was testing so you know what I am talking about:<br><br>&raquo;<A HREF="http://www.theregister.co.uk/2004/04/19/nextel_wireless_broadband/" >www.theregister.co.uk/20 &middot;&middot;&middot; oadband/</A><br><br>And here is an article from the time here on DSLR explaining speeds and the lower latency:<br><br>&raquo;<A HREF="/shownews/38350">3G Killer?</A><br><br>While I was referring to Sprint's plans to offer WiMax, of which Sprint's current EV-DO has NOTHING to do with, you had to bring up something irrelavent. Additionally you are mixing the three technologies (OFDM, EV-DO, and WiMax) into this post. While I agree that EV-DO should stay as it is tested and proven, by now, OFDM would have been tested and ether proven or rejected even though WiMax hasn't hardly been looked at.<br><SMALL>--<br>FWD#: 223611</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Maybe-18505575</guid>
<pubDate>Thu, 14 Jun 2007 13:42:00 EDT</pubDate>
</item>
<item>
<title>Re: Maybe...</title>
<link>http://www.dslreports.com/forum/Re-Maybe-18505479</link>
<description><![CDATA[Time4aNAP posted : <div class="bquote"><SMALL>said by <a href="/profile/295948" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=295948');">ropeguru</a>:</SMALL><BR><BR>They should have kept trials going with the technology Nextel had started using.</DIV>What technology?  That's news to me!<br><br><div class="bquote">Seems to me it had excellent speeds and, most importantly, low latencies.</DIV>Hold on, you just said that that it was only in the testing stage.  How would you know how well it would work?  In contrast, Sprint's EV-DO is here, now, in production.  And it works very well.  WTF???<br><br><div class="bquote">But, no, they had to nix it immediately because it was Nextel's project and what Sprint already had in the works was apparently sooooo much better.  :uhh:</DIV>Ah...do you mean to say "because it is <I>Motorola's</I> proprietary (and co$tly) technology"?  And yes, an existing mobile data system that's working right now <I>is</I> far superior than a proposed one that's not working at all.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Maybe-18505479</guid>
<pubDate>Thu, 14 Jun 2007 13:27:50 EDT</pubDate>
</item>
<item>
<title>Maybe...</title>
<link>http://www.dslreports.com/forum/Maybe-18504317</link>
<description><![CDATA[ropeguru posted : They should have kept trials going with the technology Nextel had started using. Seems to me it had excellent speeds and, most importantly, low latencies. But, no, they had to nix it immediately because it was Nextel's project and what Sprint already had in the works was apparently sooooo much better.  :uhh:<br><SMALL>--<br>FWD#: 223611</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Maybe-18504317</guid>
<pubDate>Thu, 14 Jun 2007 09:40:19 EDT</pubDate>
</item>
</channel>
</rss>
