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: Beta Testers Required


  • Subject: RE: Beta Testers Required
  • From: steve.cooper@xxxx
  • Date: Thu, 21 Aug 2003 12:42:00 +0000


Personally, what I think is missing is a list of what a device needs to do.

What do I mean by this? Well, I've not been following the scene much lately
and if I want to start making a xAP device firstly I need to understand the
spec. But for me it's all a bit long winded, what's required, what's
optional etc. What would be ideal is if there was a some minimum
operational criteria say for a basic, moderate and advanced xAP device. A
sort of checklist for a developer to go down and check if his device
supports all the requirements for a basic xAP device, say

1. Heartbeat
2. Respond to Requests
3. Send message on event

etc.

With an example for each message. That way it's nice and clear what I need
to code and what I don't.

S.



-------------------------------------------------------------------------

The information contained in this message is confidential and may be
legally privileged. If you are not the intended recipient, please do not
read, copy or otherwise use it and do not disclose it to anyone else.
Please notify the sender of the delivery error and then delete the
message from your system.

Any views or opinions expressed in this email are those of the author only.

Communications will be monitored regularly to improve our service and for
security and regulatory purposes.

Thank you for your assistance.

-------------------------------------------------------------------------






xAP_Development Main Index | xAP_Development Thread Index | xAP_Development 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.