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: Re: xPL announcement/description protocol -- was xPLDiag


  • Subject: RE: Re: xPL announcement/description protocol -- was xPLDiag
  • From: "Tony Tofts" <tony@xxxxxxxxxx>
  • Date: Fri, 23 Sep 2005 10:34:26 +0100

> Even if an app is
> already configured and starts straight away, if it starts
> before the hub it could be up to 9 minutes before the hub
> receives the next hbeat from the app and starts sending xPL
> messages to it - and that is not good.

I agree it's not good, but I also think it's incorrect?

1) if hub starts after the app, the next hbeat is at most 5 minutes away
(so
5 minutes max wait, assuming default interval)?

2) hubs are mean't to restore the list of known clients on startup, so
other
than a new app (which would be in config mode anyway) they should broadcast
to all previously known clients? Ok there are exceptions, e.g. if app
closes
first I guess this may get removed from the hub list - so I feel a more
robust method would be for hubs not to delete directly on hbeat.end, but
flag it and delete on expiry or hub exit (if this is sooner)?

Regards
Tony




xPL Main Index | xPL Thread Index | xPL 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.