Re: how to control broadcasting from client machines?
- From: "Nico" <nkadel@xxxxxxxxx>
- Date: 18 Oct 2006 13:05:34 -0700
Ertugrul Soeylemez wrote:
I don't know of any other operating system, which has the need to
broadcast the same information periodically, loading the network with
garbage. Only Windows is such a dumb p.o.s., such that it should become
forbidden world-wide -- at least for security reasons. I'm sick of
worms and bot-nets.
Well, it's not an OS problem. It's a price/penalty/performance problem.
Some smartass over in the Windows decided they could make things
"accessible" by broadcasting blindly, got something they wanted out of
it, and didn't have to pay the cost. It's kind of like spam that way:
as long as the bandwidth is there, people will use it pretty blindly
and then whine when it gets cut off because of some "feature" they
want.
The damage can usually be restricted by setting up networks on
different subnets, with a network switch capable of doing it
gracefully. Putting the broadcast related services, such as certain
types of video servers, on their own subnet is particularly helpful.
.
- Follow-Ups:
- Re: how to control broadcasting from client machines?
- From: Ertugrul Soeylemez
- Re: how to control broadcasting from client machines?
- References:
- how to control broadcasting from client machines?
- From: smart
- Re: how to control broadcasting from client machines?
- From: Jeroen Geilman
- Re: how to control broadcasting from client machines?
- From: smart
- Re: how to control broadcasting from client machines?
- From: Jeroen Geilman
- Re: how to control broadcasting from client machines?
- From: Ertugrul Soeylemez
- how to control broadcasting from client machines?
- Prev by Date: Re: what happens when bash_history reaches its limit?
- Next by Date: Re: what happens when bash_history reaches its limit?
- Previous by thread: Re: how to control broadcasting from client machines?
- Next by thread: Re: how to control broadcasting from client machines?
- Index(es):
Relevant Pages
|
Loading