Re: Re: xPL Monitor: triple msgs

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

Hi Tom,

> I changed my setup so that I can test/modify the xPL Hub code.  Both
> VMWare virtual network adapters are enabled and everything runs
> smoothly.
> There is only a minor update necessary to make the socket bind to a
> specific ip-address.  The ip-address to bind to should be a
> configuration parameter IMHO.

Yep, I'm guessing you changed the IPEndPoint to just bind to a specific IP,
rather than IPAddress.Any.

I'll make this a configurable item for those who need to specify a binding
IP.

> In a pc with more than 1 network card
> the xPL Hub listens to all cards, no ?  In a real world scenario you
> probably don't want this.

It really depends on the user's set-up - binding to all interfaces works
well for 99% of users, and avoids them needing to know what their primary
address should be - it's not easy to reliably determine a host's primary IP
address - especially where dial-up networking is involved.

Personally, I think the most robust approach is to continue to bind to all
interfaces by default, and make it easy for those users who have more than
one network interface to specify a primary IP to which the hub should bind.

> (In fact, I think I saw a few other possible improvements, but I
> better shut up being a newbie on the list ;-)

Please feel free to make any suggestions - it's nearly 2 years since the
hub was written - and the VB.NET version was itself taken from Tony's VB6
version which itself had been through several phases of development.

Regards,

John