Not sure how hard this would be (never tried it) but couldn't we set up an
admin page and password protect it?
Also, as a thought, it might be easier to keep the file code out of the
daemon and just use perl. This way the actual amount of memory used by the
obs daemon would be less, and it would be alot easier for people to
customize.
I know perl is slower than c but I don't think that's really an issue in
this case. Anyone out there make a good case for keeping the add/remove file
code in the daemon?
-F
-----Original Message-----
From: Mayhem & Chaos Coordinator [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 29, 1999 1:44 PM
To: [EMAIL PROTECTED]
Subject: Plans for the next release
Ok, here are the features that I intend to implement for the next release of
Obs:
1) Incoporate Frank's addfiles.pl script. Once I get done with this script
it will parse data out of the filename (using a configurable format) and
parse data out of the ID3v1|2 tags.
2) Create a script that will rename the files/directories according to the
specified file naming scheme specified in the config files. Possibly even
write the meta data back to the ID3v1|2 tags.
3) Improved perl module install process. (Seperate the install from the
regular make process) I'll even try to bundle the dependent perl modules
into one ueber perl module installer to make the process easier.
4) Improved docs: clean up the web pages, fix some bugs in the install docs,
5) Have the cgi-perl scripts generate ALT tags for each button that can be
clicked
Already done are:
1) VBR streaming
2) Editing database information via the browser interface
3) Improved install scripts
4) Compatibility with the latest perl modules
The database editing capabilites (admin mode) must be turned on via the
ObsDefs.pm file -- this is pretty lame. I need to find a better way to
enter/exit the admin mode -- anyone have any suggestions on how to best do
this?
--ruaok Freezerburn! All else is only icing. -- Soul Coughing
Robert Kaye -- [EMAIL PROTECTED] http://moon.eorbit.net/~robert
