-=[Juztin]=-
04-14-2004, 09:02 AM
What's up every1,
Just curious if there are any PHP enthusiasts on the forum. If so, I've been thinken about making a web controlled mp3 streaming server and was wondering if anyone would also be interested in helping write the code. I'm gonna start working on it on my weekends. What'd I'd like to see feature wise:
*One mp3 stream (reduce comlexity process wise) per server
*Ability to select MP3's by Artists/Album/Track
*Save as playlist
*Upload mp3's to contribute to central playlist
*Download mp3's if they like what they hear
*FUNDMENTAL- Stream Mp3's they select on the fly in real-time
*Multiple people can login but of course the stream will not allow the already streaming mp3 to be cut-off for a new stream, but rather insert directly into the playlist (less vote-system applies)
*Delete next-in-line mp3 to be streamed by a vote system if more than 1 user is logged in
*Cut-off current playing mp3 if only 1 user logged in or vote system allows for action
*Multiple people to be logged in and chat with each other
*Upload/Download files that are in a public "sandbox" (automatically be pruned every 5 days)
*Provide full anonomity with no logging of IP addresses anywhere in the web system (this does not take into account apache though or any 3rd party apps which may be running)
*Provide security for username & password
*Provide encryption/decryption on sanbdox for files stored on system through OpenPGP support
*Provide ability to upload/download files through HTTP/FTP/XML stream/ or ASCII paste
*Provide image gallery w/ comment system & automatic image thumbnails
*Provid ability to fragment files and hide on a needed basis throughout system, the recall and rebuild. (For all the van eck fans out there)
*Provide ability to email out files if needed to supplied addresses, also the fragment ability appear here as well, maybe even email out fragments in raw ASCII format and rebuild when all emails are obtained on the remote end.
*Ability to upload/download files through actual chat as it happens, devise some kind of tracking system to keep track of waht's chat and what's not, can even include multiple chats to allow for faster transfer rates.
*Possible redudancy if backup server is present
*Possible inclusion of other servers running on internet, kinda like a distributed system!
IF this was to somehow happen over time:
[distrib. mp3's/files/chat/storage/fragmentation]
[eventual goal of making system as autonomous as programmingly possible]
[resiliant, auto-healing, and eventually even auto-installing on willing servers]
[ability to auto-create code on an as needed basis to fix things]
PHP right now, but other languages welcome provided I can learn em ;-)
Any features anyone else could think of?
--j2
(I need to get back into PHP so figured this would be a great way)
I'd also ideally like to have PHP5 used as the base language due to it's extended OOP support.
Oh yeah, OOP will be a requirement of the underlying code, we need modularity and a solid abstract design for each layer of the app and how it interacts with each other and the other components needed to stream the software, store the files, etc...
Just curious if there are any PHP enthusiasts on the forum. If so, I've been thinken about making a web controlled mp3 streaming server and was wondering if anyone would also be interested in helping write the code. I'm gonna start working on it on my weekends. What'd I'd like to see feature wise:
*One mp3 stream (reduce comlexity process wise) per server
*Ability to select MP3's by Artists/Album/Track
*Save as playlist
*Upload mp3's to contribute to central playlist
*Download mp3's if they like what they hear
*FUNDMENTAL- Stream Mp3's they select on the fly in real-time
*Multiple people can login but of course the stream will not allow the already streaming mp3 to be cut-off for a new stream, but rather insert directly into the playlist (less vote-system applies)
*Delete next-in-line mp3 to be streamed by a vote system if more than 1 user is logged in
*Cut-off current playing mp3 if only 1 user logged in or vote system allows for action
*Multiple people to be logged in and chat with each other
*Upload/Download files that are in a public "sandbox" (automatically be pruned every 5 days)
*Provide full anonomity with no logging of IP addresses anywhere in the web system (this does not take into account apache though or any 3rd party apps which may be running)
*Provide security for username & password
*Provide encryption/decryption on sanbdox for files stored on system through OpenPGP support
*Provide ability to upload/download files through HTTP/FTP/XML stream/ or ASCII paste
*Provide image gallery w/ comment system & automatic image thumbnails
*Provid ability to fragment files and hide on a needed basis throughout system, the recall and rebuild. (For all the van eck fans out there)
*Provide ability to email out files if needed to supplied addresses, also the fragment ability appear here as well, maybe even email out fragments in raw ASCII format and rebuild when all emails are obtained on the remote end.
*Ability to upload/download files through actual chat as it happens, devise some kind of tracking system to keep track of waht's chat and what's not, can even include multiple chats to allow for faster transfer rates.
*Possible redudancy if backup server is present
*Possible inclusion of other servers running on internet, kinda like a distributed system!
IF this was to somehow happen over time:
[distrib. mp3's/files/chat/storage/fragmentation]
[eventual goal of making system as autonomous as programmingly possible]
[resiliant, auto-healing, and eventually even auto-installing on willing servers]
[ability to auto-create code on an as needed basis to fix things]
PHP right now, but other languages welcome provided I can learn em ;-)
Any features anyone else could think of?
--j2
(I need to get back into PHP so figured this would be a great way)
I'd also ideally like to have PHP5 used as the base language due to it's extended OOP support.
Oh yeah, OOP will be a requirement of the underlying code, we need modularity and a solid abstract design for each layer of the app and how it interacts with each other and the other components needed to stream the software, store the files, etc...