Re: Multi-block message bodies

[Stuart Booth]

On Wed, 11 Jun 2003 12:54:15 +0100, "Kevin Hawkins"
<<a
href="/group/xAP_developer/post?postID=MOQEOGVgF82_I83TP8Mb7Crsl3mvGfYco5UkMDqqTz85CBf2qOyAVBQq6Utp2i-b5iVyX1-hFeKjwNlK2TE">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.

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!

So the developer's code can check things as they wish, and a few
classes which encapsulate target/source addresses make wildcard
matching relatively easy.

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=14BxLhqnCas0r_qcXd8lk8vlpikvKM_d3--li-emMRVQpT011JUxhqoCT68iNFtlxvyEt-YbWyUAOKa8IJHb-L7z">stuart@x...</a>