Re: Displays round the house - architecture...

["PatrickLidstone" <patrickl@xxxxxxx>]

--- In ukha_d@y..., Stuart Poulton <swp@s...> wrote:
> Hi again 
> 
> In terms of protocol, I really urge people to take a look at SNAP,
for the 
> following reasons.

I agree with this in principle - if there is a standard which meets 
the functional requirements then use it. 

I don't think the complete functional requirements for the network 
layer are clear - but I guess at a minimum it must be:

- bridgeable across multiple physical media, supporting at least 
serial and TCP/IP over ethernet
- minimal footprint on embedded device
- support error detection (and optionally correction?)
- support a full naming service
- be simple to manage (eg. support autodiscovery of new devices on 
the network in a DHCP like way)
- support broadcasting (or ideally multicasting)
- support status requests/positive acknowledgement (can also be
implemented at an application level)
- impose sensible limitation on number of concurrent devices and 
message size
- be licence free / cheap to implement in terms of hardware
- ... and no doubt there are more

My previous post, though, primarily related to the message format at 
the application layer. Are there any suitable standards which define 
the semantics of what we are trying to achieve here? I'm not aware of 
any but haven't looked very hard.

Patrick

Yahoo! Groups Sponsor

ADVERTISEMENT

For more information: http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx 
Subscribe:  ukha_d-subscribe@xxxxxxx 
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx 
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.