Re: Topic 5: targetting Based on UID

[Stuart Booth]

On Tue, 10 Jun 2003 18:35:21 +0100, "Kevin Hawkins"
<<a
href="/group/xAP_developer/post?postID=YQCdhwM9OGZyiz8itapLJy4dckB5ocp2LYrA0Ulac2CUUzOaBLCxrxsZFpb045kF-ETiwQ7evQmyJVuBwv45HA">lists@u...</a>>
wrote:

> How about a low power switch being able to just target
>a lamp based on UID - now again the low power switch can make the same
>savings - but actually it can't because it would have to send the full
>target address as well. Are there ways around this ?? Well yes, but
they are
>not tidy. You could enlist a 'helper' (cache) on a xAP network that
>monitored any devices targeting just based on UID and filled in the
targets
>full address as well, or you could just allow it as a device
restriction. My
>feelings now are that the latter is unacceptable and the former
>overcomplicates the whole operation of xAP.

So a helper app would detect a message with only UID targetting in it
(no full target address).

A lower-end device hunting only on target UID would pick up the
original message.

A higher-end device looking for either would pick up the original
message.

The helper app would detect the lack of a full target address and
would resend the message, replacing the target UID with a full target
address.

A higher-end device looking for either target UID or target address
would not be able to determine that it was repeated unless the message
was tweaked in some way to indicate that it had been
modified/repeated.

A higher-end device looking only for target address would pick up the
repeated/filled-out message and be happy.

Seems to me that this helper app could maybe automatically build up a
picture of UID->target address mappings??? But there's bound to be
some ambiguity, without having thought about it too deeply.

S
--
Stuart Booth
xAPFramework.net - a reusable xAP framework for .net

<a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>
<a
href="/group/xAP_developer/post?postID=kORC5mri4CNcebLPexkW8gpz_a0ZQeANytC-ahjyRKEBKNaLzB67vBD80i93KW5qVQc9ySFAf5ClFbb0PkFT0w">stuart@x...</a>