RE: Re: [Project] Kbd/LCD device

["Broadfoot, Kieran J" <Kieran.Broadfoot@xxxxxxx>]

I think multicasting would be an interesting thing for John to bash onto
his
rabbit ;-)

I think the use of multicast/broadcast should be limited within the system
itself though.  I like the idea of direct comms between devices and console
etc but because it helps ensure the integrity of the system.. We dont end
up
with the wrong devices in the wrong zones etc due to bad programming or
devices listening on the wrong ports etc.  Not to suggest we would any of
the above but I would prefer to use multi/broadcast just for the discovery
phase.  The "hello, im a light controller" component.

thanks
kieran

-----Original Message-----
From: Ant Skelton [mailto:fourstringmother@xxxxxxx]
Sent: Monday, June 04, 2001 4:40 PM
To: ukha_d@xxxxxxx
Subject: RE: [ukha_d] Re: [Project] Kbd/LCD device



> Ahh multicast... now that could be an interesting
> option.  Well worth
> considering.

Yes, multicasts are the way to go. Broadcasts are
pretty much frowned upon these days in protocol design
for all sorts of reasons, among them their inability
to cross network boundaries, the possibility of packet
storms as a result of poorly configured devices on the
net, the additional workload they place on network
attached devices (particularly lightweight ones like
we're discusssing) and the fact that not all link
layers or network layers support them. IPv6 for
example, does not.

cheers

ant


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year!  http://personal.mail.yahoo.com/



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/




Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/