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]

New Rio Client - Stage 2 Complete


  • Subject: New Rio Client - Stage 2 Complete
  • From: Tony Tofts
  • Date: Tue, 10 Feb 2004 07:23:00 +0000

Hi all,

Stage 2, the scanner, is complete for now (still needs id3v1, and testing
on
a deep nested folder structure)

It provides manual purge/scan options (for the server web interface and xPL
server commands)

Also timed automatic scanning (and a purge can be planned to be performed
on
demand in advance at the same time as the timed scan)

It recursively walks the folder structure during scanning, as this saves
having to store the folder structure in memory or a database table.

You can configure as many base paths as required, so music can be spread
out
between folders/drives/network shares

Next up is Stage 3

This involves starting work on the new Rio client software and it's
interaction with the client control software in the client/server app.

Basically this part is:
Panel/remote commands being passed from Rio to server
Stuff to display being sent to the Rio from the server

This is probably the most involved part of the whole project, so will take
a
while.


On the xPL front the original plan was to match the Rio xPL instance to the
ip address, but to allow for networks where an external dhcp server might
be
used that doesn't support mac/ip address mapping (like an ADSL router) the
server will map the xPL instance to the Rio's mac address. This has the
advantage of ensuring a particular Rio always gets the same xPL instance
regardless of ip address. At least I think I can do this!

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.