requests.txt, mysql support, random thoughts

Hi guys,

For some reason email from this list keeps getting lost in my maze of 
junk filters, so if you haven't gotten a reply, sorry.

Someone requested a "requests.txt" file. That is an interesting 
thought, though I wonder if it wouldn't make more sense to have the 
ability to weight a song?
Doing something that would order the requests though would require a 
dispatch that could sit and make use of any other dispatch (if you 
don't know what a dispatch is... go read the FAQ). Not impossible, but 
not something I have currently planned.

New work:

MySQL dispatch will now support pushing the entire mp3 into the 
database. I will support both the older text based protocol and the 
newer binary protocol in 4.1. This should make it plenty fast and will 
resolve the issue where your MP3's get moved and suddenly the files no 
longer can be found. I am designing this around how MySQL delivers 
binary support so it will be plenty fast. I would love to hear form 
user's how MySQL 4.1 is working with what is in CVS. Make sure to 
enable the binary protocol when you run configure.

I have also left notes for whomever patches postgres so that the same 
can be done there. Personally I would find it to be fairly interesting 
to see which DB could pump out mp3's faster. The postgres support has a 
very poor row -> mp3_data implementation and chews up a lot of memory 
(I would suspect that if a user stayed connected for too many hours you 
would run out of memory).

I also added rss2 support today. I will try to add embedding tags while 
I am at it, so that podcasting can be supported. Not sure about getting 
ATOM done just yet.

1.1 has a lot of code that has been reworked to use less memory. It 
(and another feature I will not talk about just yet) are my prime 
motivators at the moment for coding on mod_mp3.

I used .4X for years without issue, but my mp3 collection has just 
gotten too big for it to easily handle. So, getting mod_mp3 to use less 
memory is a big motivator for me.


	-Brian