On Thu, 04 Aug 2005 13:12:02 -0500, David Maynard
<nospam@private.net> wrote:


>> No it is still a reduction to whatever extent you transfer
>> data with it. Idle networks aren't a bandwidth problem,
>
>An idle network doesn't need any protocol at all so the point is moot.

It's still valid because "chatter" that isn't exceeding
network bandwidth potential in conjunction with other
traffic or increasing latency is not a negative thing.

>
>However, netbeui isn't idle when the network is idle. It's perpetually
>bombarding the thing with 'synchronization/identification' traffic.

"Bombard" is a bit strong, but even so, we don't have to
care what it's doing with the network is idle, only that
during actual transfers, it's faster, and that speed
difference in actual transfers is the significant parameter.

>
>> the
>> focus needs be on transfers, their efficiency and duration.
>> Of course there are far larger gains seen from things like
>> moving from 10Mb to 100Mb, but there's not a lot of point in
>> itemizing every possible network performance limiter when
>> the topic was already isolating one parameter.
>
>I have no idea what the point in there was supposed to be if it wasn't
>that, in the overall scheme of things, any 'efficiencies' imagined for
>netbeui don't justify keeping it.
>

No, it was tha there are other ways to get more gain if one
were to change only ONE thing, though such an artificial
limit isn't reasonable to assume either.