The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: Re: "Toggle" command


[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: James
  • Date: Wed, 24 Sep 2003 00:52:00 +0000


>
> We need to push forward on the issue of datagrams that may need more
> than 1500 bytes of data - is this causing you a few problems currently
? -
> I saw an adjacent post -
>
In news and traffic if the datagram is over 1500 then I simply reduce
the number of blocks theat are sent. In watcher if the limit is hit the
the message is sent without the process list.
The datagram sizes are an issue, but not a big one. I would say go for:
1,DHCP like config system
2,Basline Status request and reporting
3,Core schema like display
4,Website/howtos/big PR push
(in no order)
before worrying about multipart messages. I think the time is now for
getting xAP in to real public circulation. Once end users start using
systems, new ideas/ways/concepts are realised. These ideas, plus
multipart messages etc, would be the basis of v1.3 . xAP is good to go
now, well good once the above are sorted!!

James



> Kevin
>
>
>
>
> To unsubscribe from this group, send an email to:
> <a
href="/group/xAP_developer/post?postID=riaR2MXjdudMFoLSzVGokljybArAiFSq2_70bO5KG_PxqObXbJz8TSpz_LwHACJqbXUVlkootjR8IXlttVRkuh3rsp-a7p5UG8ZZydaChesI17g">xAP_developer-unsubscribe@xxxxxxx</a>
>
>
>
> Your use of Yahoo! Groups is subject to <a href="http://docs.yahoo.com/info/terms/";>http://docs.yahoo.com/info/terms/</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.