RE: xPLHubs (again!)

["John B" <home-automation@xxxxxxxxxxxxxxxx>]

Hi Mal,

The V3 hub keeps it's client list in the Windows system folder, in a
file called xplhubclients.bin.
This means that every V3 app on the PC can share the file.
So, if you're not the active hub, then it doesn't matter, because
whatever is acting as the active hub will be updating the file (provided
it's a V3-aware hub).
If you subsequently take over as the active hub, the file will be up to
date for you.

The only problem is that Tom used a binary file, which I think (though
I'm not sure - would have to check the code) is a serialised object from
.NET, so it may not be very easy to read/write the same file from a
non-.NET environment.

Maybe we should considder an XML file format for the shared hub clients
list? That way every V3-aware hub can share the file, regardless of
development environment.

Thoughts?

Regards,

John


> -----Original Message-----
> From: Mal Lansell [mailto:mlansell@xxxxxxx]
> Sent: 13 March 2005 12:46
> To: ukha_xpl@xxxxxxx
> Subject: [ukha_xpl] xPLHubs (again!)
>
>
>
> I'm currently adding V3 hub functionality to my C++ lib, but
> I'm wondering how I should deal with updating the client list
> when not the active hub.
>
> If my hub is a built-in part of another xPL application, I
> can use the messages received to keep the client list up to
> date.  However, if the hub is a standalone, it won't receive
> any messages from the active hub unless it sends heartbeats -
> something that hubs should not do.
>
> How has this been dealt with in the new .NET hub?
>
> Mal
>
>
>
>
>
>
>
>
>
>
> xPL Links: http://www.xplproject.org.uk http://www.xplhal.com
> http://www.xpl.myby.co.uk To
Post a Message:
> ukha_xpl@xxxxxxx To Subscribe:
> ukha_xpl-subscribe@xxxxxxx
> To Unsubscribe:  ukha_xpl-unsubscribe@xxxxxxx
> Yahoo! Groups Links
>
>
>
>
>
>
>
>


xPL Links: http://www.xplproject.org.uk http://www.xplhal.com http://www.xpl.myby.co.uk
To Post a Message: ukha_xpl@xxxxxxx
To Subscribe:  ukha_xpl-subscribe@xxxxxxx
To Unsubscribe:  ukha_xpl-unsubscribe@xxxxxxx