RE: Re: Multi-block message bodies

[Kevin Hawkins]

> -----Original Message-----
> From: Patrick Lidstone [mailto:<a
href="/group/xAP_developer/post?postID=EdnNptb7NLtP97Jg-aIQocVVg6RdtaAIYjJtKQKzTPVyW9wX4mYslc1gVFjzwQe91R446Mmy3MZHKfs">patrick@l...</a>]
> Sent: 16 June 2003 19:32
> To: <a
href="/group/xAP_developer/post?postID=NbrwkMNAbyLYJ9ztO0E58ZBKrRdGScKUwcMzXTBPW-JWt8s3LDVodVwbvhw829rYHv3lkroZ2wnLnN1DoaKVDh86qdE">xAP_developer@xxxxxxx</a>
> Subject: [xAP_developer] Re: Multi-block message bodies
>
> >
> > However think on say a 4 channel dimmer status response
> >
> > Status.response
> > {
> > Channel 1 =50%
> > Channel 2 =20%
> > Channel 3 =30%
> > Channel 4 =0%
> > )
> >
> > or if channels were named
> >
> > status.response
> > {
> > Lounge=50%
> > Hall=20%
> > Kitchen=30%
> > Outside=0%
> > )
>
> Or...
>
> status.response.lounge
> {
> lighting=50%
> }
>
> status.response.hall
> {
> lighting=20%
> }
>
> etc.
>
> For me, this works better from a coding perspective. It allows for an
> infinite number of "channels" subject to maximum message
size, and

Given this move towards multiple bodies a way of chaining or showing
continuation of a xAP message would be nice to define. Sort of fits in with
the sequencing discussion too

> allows for nice encapsulation. If my dimmer pack was later upgraded
> to allow for - oh, I don't know, occupancy detection say - then I can
> extend the message to do:
>
> status.response.hall
> {
> lighting=20%
> occupancy=1
> }
>
> I agree that I could also slice it: status.light / status.occupancy -
> but it's not as intuitive to me, anyway - I would like to have the
> flexibility to be able to do things both ways, and would choose to
> group by location in the first instance.
>