Re: Conf file architechture?

So I just checked some changes in for
volume defaults (and added an entry

to the slimp3.conf file for it) but it occurs to me that there might
be a

smarter way.

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. :)

Absolutely. The server options probably should include
defaults for the player options, then the server should save away
player settings across server launches on a per-player basis. To
the user, the players should each appear to have persistent
state.

Anyway, I think we should we be
specifying settings such as volume and/or

alarmclock on a per-client basis in the config file. I'm not sure how
best

to go about this right now though. Perhaps the last person to
re-write

the server code could take a shot at explaining the best way?
Maybe

reimplement my volume changes as a
"best form" example?

I'll give it a shot. Could you write a bug up against it to
keep me honest?

-dean