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: Multi-block message bodies


  • Subject: RE: Multi-block message bodies
  • From: Kevin Hawkins
  • Date: Wed, 11 Jun 2003 15:23:00 +0000



> -----Original Message-----
> From: Stuart Booth [mailto:<a
href="/group/xAP_developer/post?postID=4m3-uHxSrbINHLnt2X_I4sH8DdwPFVEthrZ2HDczLtqoodvnz2WcykPcQXRmTmaAnVUFEOXiqT3SDJcWcA">lists@x...</a>]
> Sent: 11 June 2003 13:27
> To: <a
href="/group/xAP_developer/post?postID=m_8FisbjaYMBpqvmqZApe8M_b9diN3yE_2fjPSi0pIJbrjkqMDqMLFsbo_rSO3C0tbO2lsFzQ-L1CpjUPLn-QyNMSbYT2NBe">xAP_developer@xxxxxxx</a>
> Subject: Re: [xAP_developer] Multi-block message bodies
>
> On Wed, 11 Jun 2003 12:54:15 +0100, "Kevin Hawkins"
> <<a
href="/group/xAP_developer/post?postID=wfk6gEKr664cx9UuokMn2fmD3-RP5dOoWGXG3UpFa6x0539hgHFbSxHSIaQVr1M43X2rm8gIrxAKEoyd2CZrLuc">lists@u...</a>>
wrote:
>
> > > Eek! "Block.Name.1.1" and
"Block.Name.1.b"'s?!
> >
> >I think the key thing here is that wherever a dot hierarchy is
> allowable we
> >have not artificially restricted it in depth - as in the
class.type or
> >bock.header areas
>
> I think I just need to check that I support it. You pointed out to me
> a while back that Class.Type can be multiple depth and I added support
> for that, which I hadn't realised before. Not yet sure if I did the
> same for Block names. No biggy though.
>
> > > That's how I deal with such repeated cases of Data=This and
> Data=That
> > > in a single message block.
> >
> >What sort of circumstance does this occur in ? I am trying to
think of
> an
> >instance when it is necessary
>
> I haven't seen this. But if you built up a message using my framework,
> the 2nd occurence would wipe out the value of the previous occurence,
> as you expected.
>
> So you could form a message (but not with xAPFramework.net) e.g. by
> string concatenation, that did that, but it would be lost when read in
> by my framework.
>
> Block.Name
> {
> Data.1=...
> Data.2=...
> }
>
> ...would work fine.

Really the .1 .2 defines distinct names though (could be 'Richard' and
'Judy') and doesn't imply any similarity of the data though (data.1 could
be
a temperature and data.2 a news headline) I thought you were trying to
present a case for indexing repeats of the same data type.
>
> I have a special 'Test' project that executes a large series of
> automated tests on my various xAP classes in my framework SDK. Not
> complete yet, I add to it all the time as I discover bugs/features or
> add new features. I'll insert this stuff as a further test I think.
>
> > > This is something I plan on leaving to the developer that
uses my
> > > framework. Their app can pick up the Target line and then
put the
> > > value into an instance of a xAPTargetAddress object. From
there
> they
> > > get all the various benefits of that class.
> >
> > If you supported targeting of message blocks within the framework
> >wouldn't it be easier to return to the user a calculated target
> address that
> >makes use of the combinational function of the logic - perhaps as
well
> as
> >the target info in the header and the target info from the block
> separately?
>
> Not quite sure I follow you here. It's really up to the developer's
> code to do the targetting at the moment. My framework merely says
> "Here's a message" and leaves it up to the app. There are
some
> additional message header matching facilities available but that's as
> far as I've taken it thus far.
>
> I do have thoughts to add some automated addressing events
("Here's a
> message that's targetted at you"), but just haven't had the
pressing
> need for this yet. It's on the ToDo list amongst a pile of other
> items!

That last comment ' this is targeted at you' is exactly what I meant with
"
If you supported targeting of message blocks" - me not making it clear
I was
talking about receiving a targeted message - we're now on the sama
wavelength

K







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.