RE: Re: IMPORTANT xAP Basic Status and Control

[Kevin Hawkins]

Hello Ian,

Long time no hear.. welcome back...

Yes - I think you have it about sussed there - everything you say is
correct.
The only issue is whether the two status messages could be combined
into one by incorporating the basic status body with your own in a multi
body transmission - essentially meaning one message with both bodies. I
think you dislike multiple bodies though if I remember correctly. Overall
though I don't see this as particularly advantageous although there may be
code space implications for or against this. It is probably of particular
magnitude only when a complete status response for all I/O is sent. In that
case trying to combine two may lead to packet overflow.
Maybe I am just saying that the body part must be included in all
status messages (and not really defining a schema as such).
How I sort of see it is that this is basic functionality that
enables everything to work together seamlessly and then you layer fancier
schemas on top of that to enhance the feature set of your product. My C-Bus
units for example will typically be controlled by 'name' rather than the ID
number but this allows for that to work as well.

You can make your own choice on the old chestnut of whether

{
device=TableLamp
state=ON
}

or

{
TableLamp=ON
}


Is correct...

Kevin



> -----Original Message-----
> From: Ian Bird [mailto:<a
href="/group/xAP_developer/post?postID=Ni5W1TRML-cIfLoDSRwcy7r2LwQMuyxAnr27FUUZ0dSM2sDTZQ5AnYVy872G1YA8IVDJ_CxpDz8qIgJj3g">Ian@M...</a>]
> Sent: 21 October 2003 18:29
> To: <a
href="/group/xAP_developer/post?postID=trJEVMJBuHquVEVjskSY-NyKbKNTArxDixmghyNz7Ba3rOygpw6ziv-KJuIAUyAx7sGRp8-n4rVFcj2q-mVQgNRf-GmxbA">xAP_developer@xxxxxxx</a>
> Subject: [xAP_developer] Re: IMPORTANT xAP Basic Status and Control
>
> Hi Kevin
>
> This is something we touched on a while back but how do you see the
> basic schema in relation to other supported schemas for a product. I
> am thinking primarily of status more than anything at the moment.
> Will a product have to send both a basic status message and a more
> comprehensive one in response to stimuli i.e. something changes or a
> request. What order will these have to go out in? I do kinda assume
> though that two messages will be sent, one with the basic schema and
> one with the proprietary schema.
>
> For example my I/O board has a detailed status schema for both the
> outputs and the inputs (yep, 2 schema or is that schemi?). So, if a
> timer expires on one of the outputs I would need to send two status
> messages, one giving the basic 'output x = off' or whatever is the
> correct format. The second would be my output schema which would say
> something similar in a different format possibly with some other
> information (no examples off hand).
>
> I think things are simpler in the case of a status request as it will
> either be a basic request which would get a basic reply or a
> proprietary one which would get the detailed reply. Neither would
> trigger both replies.
>
> Finally for the time being, if the basic schema say turns on an
> output I assume I will send a status message by way of a reply
> saying 'output x = on'. I would then also send another status message
> saying 'output x = on <LF> timer=00:00:00' which is the more
detailed
> version and needed for a dedicated plug-in or controller.
>
> Is this how you see it all integrating?
>
> Sorry if this is a little disjointed but it has been a while since I
> have been able to spend any time on my projects.
>
> Thanks
>
> Ian
>
>
>
> ------------------------ Yahoo! Groups Sponsor
---------------------~--
> >
> Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
> Printer at MyInks.com. Free s/h on orders $50 or more to the US
&amp;
> Canada.
> <a href="http://www.c1tracking.com/l.asp?cid=5511";>http://www.c1tracking.com/l.asp?cid=5511</a>
> <a href="http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/dpFolB/TM";>http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/dpFolB/TM</a>
>
---------------------------------------------------------------------~-
> >
>
> To unsubscribe from this group, send an email to:
> <a
href="/group/xAP_developer/post?postID=HPUucE9gpIg2jXeIfj83Y7zNpWTipAQXNLUTWG68wJtoXp2MHExQ0xPIH0cF2pDTdGo8iXttxvBO5fTU3HUrUMXOL3D58-l3NRBGfDJ8NA">xAP_developer-unsubscribe@xxxxxxx</a>
>
>
>
> Your use of Yahoo! Groups is subject to
> <a href="http://docs.yahoo.com/info/terms/";>http://docs.yahoo.com/info/terms/</a>