Re: Developing Embedded xAP Devices

["ukusaconsulting" <yahoogroupskh@xxxxxxxxxxxxxx>]

--- In xap_automation@xxxxxxx, "Neil Wrightson"
<neilw@...> wrote:
>
> Hi Kevin,
>
>
>
> Definitely have to work on the Wildcarding side of things.
>
> Can't say that I fully understand how they work. I will have to go
back to
> the doco.
>
>
>
> How is version 1.3 or is it 1.4 of the BSC doc going?

There are no plans on the horizon for a BSC v1.4 specification .  The BSC
v1.3 spec is published on the xAP Automation web site.
>
> I'm not sure if I should be using UID of FF123456 or FF.1234:56 etc
etc?
>
I hope I've outlined the difference in previous messages - totally up to
you. My recommendation is to use the new xAP v1.3 UID format but if your
device fits comfortably inside the older (published) xAP v1.2 format then
that's fine - it will be compatible.

>
>
> How about a beta version of the document.

Not at the moment - but the key changes have been well itemised here.

Kevin
>
>
>
> Neil.
>
>
>
>   _____
>
> From: xap_automation@xxxxxxx [mailto:xap_automation@xxxxxxx]
> On Behalf Of Kevin Hawkins
> Sent: Sunday, 30 August 2009 9:43 PM
> To: xap_automation@xxxxxxx
> Subject: Re: [xap_automation] Re: Developing Embedded xAP Devices
>
>
>
>
>
> Just dashing out but very quickly...
>
> Not all xAP embedded devices implement full wildcarding for their
> message reception (target=) eg the Barix Barionet cheats a little. It
> has preset matches that it checks against for the wildcards and this
> covers most eventualities.
>
> If nothing else you should recognise
> (assuming you use a three segment main address and a single segment
sub
> address)
>
> target=*.*.*
> target=>
> target=*.*.>
>
> and for your sub addresses (assuming a single level) you should
recognise
>
> :>
> :*
>
> eg
>
> target=>:>
> target=acme.device.instance:*
> Recognising when some '*'s are substituted for the segment name is
> useful too - even if it's with preset matches.
>
> BTW - although not very flexible, you can also implement wildcarding
by
> back substituting the '*' s in the target address with the appropriate
> segment name in your address, and then matching against a fixed string
> - if that's easier. You still need to handle '>' though
>
> K
>




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