[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Developing Embedded xAP Devices
- Subject: Developing Embedded xAP Devices
- From: "nwemail27" <nwemail27@xxxxxxxxx>
- Date: Sun, 30 Aug 2009 03:17:27 -0000
Hi All,
I'm developing some hardware that I would like to make xAP compatible.
So from an embedded perspective, what are people typically decoding in a
xAP message.
I.e.
1. Do you look for and validate the "xAP-header" line of the
message?
2. By the way, how many different header lines are there? I.e. I think the
"xAP-Heartbeat" is one.
3. Actually, what is this line called? Header of the Header :-)
4. What part of the header message do you normally pay attention too?
5. Do you normally just use the UID field as an address or do you also
attempt to validate the target.
6. What about wild cards? Do you handle them?
7. What about the class field? If the address/target is correct do you then
ignore the class?
I know in an ideal world, we would decode and validate every response but
in an embedded device there is only so much programming space and static
memory space.
Regards,
Neil Wrightson.
Skype : Neil_Wrightson
------------------------------------
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|