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 Hubs




---- Original Message ----
From: Tony Tofts <tony@xxxxxxx>
Sent: Thu, 9 Dec 2004 06:33:24 -0000
To: <ukha_xpl@xxxxxxx>

>
> > So long as everything "just works" out of the box -
that's
> > the most important thing.
>
> Gerry's suggestion of relying on whether a hub can bind to the port is
one I
> support myself.

True - though I don't think it would be possible for another hub to take
over instantly, as it would need to keep trying to bind to the port at
regular intervals in order to detect the loss of a hub.

> Having said that, as long as there is no compatibility issue between
the
> xpllib hub and other hubs, then I don't mind what approach is taken.

There shouldn't be.

> I do wonder though if the xpllib hub should be "off" by
default, as it means
> that (for example) if I install a new app then unless I know for sure
it's
> using the new xpllib then I won't know that at some point (say after a
> reboot) that this may of taken over hub duties...

This is a valid point.
It would mean that apps that migrated to V3 would continue to behave like
they do now (i.e. with no hub) unless the developer specifically enabled
it.

Probably better for developers to evaluate whether to enable the built-in
hub in their app before enabling it, so I'll go with setting the default to
False, unless anyone has any strong objections.

Regards,

John




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.