Re: Conf file architechture?

> I'm guessing we should be making an effort to seperate server options from
> individual SliMP3 options, even for defaults. I'd like to think I might
> have a couple of these little devices at some point. :)

Yes, per-client settings need to be saved separately.  Already we have
some state which would be good to save when the server is restarted:

- last selection for each directory (not really a config thing)
- volume
- file name / id3 display

I'd like to have system where things can be configured from the remote,
using the same sort of hierachical up/down/left/right interface to choose
config options. Some other configurabe options might be:

- language
- bass/treble
- sleep/alarm clock
- sound effects when browsing
- different UI behavior (key repeat, etc.)
- display dimming, etc.

We could put it all in one big dbm file. So the server will have
two config files:

~/slimp3.conf - just server settings, like what port for HTTP, etc.
~/slimp3.db   - all the state and configuration options for all our clients

The dbm file could be like:

10.0.1.2,lastselection,/Rock/ACDC	High Voltage
10.0.1.1,volume				80

and so on...

I actually was using dbm to save the last selection, but I had to take it
out before the 1.0 release due to some problems where the DBM file was
getting corrupted.  If you want to take a look, go back to the very first
revisions of server.pl and you'll see it - it's just a couple lines of
code.

Sean


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get your FREE VeriSign guide to security solutions for your web site: encrypting transactions, securing intranets, and more!
http://us.click.yahoo.com/UnN2wB/m5_CAA/yigFAA/rIp0lB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/