The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: wild carding the instance problem


  • Subject: RE: wild carding the instance problem
  • From: Ian Lowe
  • Date: Sun, 28 Dec 2003 21:21:00 +0000

>It was the broadcast message that i was using......

Good, good ;)

>Also do you see any problem if the instance is a fixed number of
>characters??

Well, the maximum size of the instance is 16 characters, so 17 including
an end terminator of some kind. I don't see any issue with handling this
internally as a fixed chunk of seventeen bytes.

I'm thinking through the implications, and tbh, if you are really short
for memory, and need to restrict the instance for your device to only,
say, 8 characters... I don't think that will break anything..

The main thing is to handle it gracefully: I wouldn't think it was okay
to ignore or drop a config message because the instance is longer than
you can handle. If you receive a config message asking you to set the
instance, and you truncate it, it's going to be fairly apparent to the
user what happened.

Tony? John? Does this approach present any problems for the OCX or DLL
respectively?

Ian.






xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.