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: xPLRioNet Beta 3.2s Released


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: Re: RioNet - boot problem


  • Subject: RE: Re: RioNet - boot problem
  • From: Tony Tofts
  • Date: Tue, 06 Apr 2004 16:37:00 +0000

> saw this exact problem yesterday. after shutting down the
> service & restarting it & editing the clients list

Depending on the sequence of events, this wouldn't surprise me.

In a situation as you describe it's best to reboot the rio's after
restarting the service.

In normal circumstances stopping/starting the service will just result in
the clients being forced back to the splash screen. But if you've made a
change to the clients.xml or similar then the ports the client/server think
they are using can be out of synch.

Once all the main functionality is up and running, area's like this will be
revisited to see if there are any improvements that can be made.

One option being considered is to have the server send out a regular 'where
are you?' broadcast to all clients, so they can report back their status
and
what port they are listening on.

Currently when the service starts it loads the ports for all known clients
and activates them, making the assumption that the client is there. New
clients get added as they appear. If a client is rebooted then it sends a
'I'm ready again, set me up' message, and the server returns the rio to a
known state. This seems sufficiently robust, however having somekind of
extra discovery mechanism to recover automatically from a port conflict (or
similar) would be a good idea.

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.