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: News.Report message schema in xAPFramework.net


  • Subject: Re: News.Report message schema in xAPFramework.net
  • From: Stuart Booth
  • Date: Mon, 22 Sep 2003 23:18:00 +0000

On Sun, 21 Sep 2003 22:06:20 +0100, Stuart Booth
<<a
href="/group/xAP_developer/post?postID=Z-rdQSy6foyfDkDrbnEteesBYW6-4B68FbjlTMecdREhz_ONpbTq3WpXSBZRdOQZMUCrslGuDKnpT3JVQrk">lists@x...</a>>
wrote:

>I've still got to do News.Alert but it'll share some of the code of
>course. I've added some helpful support for block name indexing to my
>framework code to facilitate this type of schema, to help keep block
>names unique.

Tonight's progress: this is all now fully built-into the xAPFramework
SDK itself. The block numbering happens automatically if you tell a
xAPMessage object to ensure it has unique block names. I've also
updated the framework test routines to test it out.

So, add one block titled "News.Feed" to form a message thus:

News.Feed
{
}

Then add another block with the same name and you end up with a body,
thus:

News.Feed.1
{
}
News.Feed.2
{
}

You can add in News.Report.4 if you want to, but I seem to recall we
were talking about keeping these sequential a while ago. I haven't
enforced this at this stage though.

James, do you always include the index number in the News.Report
schema News.Feed blocks, even when there is only the one block in the
entire message?

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=rDf4mXEwrYaUO1X0qeD3o5cxKH5nHO6EiqQ7RooxiC_0oKp83PkNG9Ra6YIDO3dWM7HBMVoTqxcs6JTuZQ">stuart@x...</a>





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.