masking on demand content urls

[Jägs]

Sorry if this has been asked/answered, but I was unable to find a similar topic using the search. Forgive me if this sounds, well, asinine, but...

I would like to know if it is possible to somehow mask the url used to access on-demand content. What I mean by this is that I would like to prevent the user from being able to access an on-demand file directly by looking at the contents of the PLS file.

Why would I want to do this? Well, I am developing a streaming media management tool for our music courses, and want users to only be able to access the on-demand content through it. We have future plans of using the system for testing purposes and do not want the on-demand songs used for this purpose to be easily distributed.

I would like to somehow give each song either a one-time-use url, or mask the url with a generic PLS url like:

http://shoutcast.school.edu/content/class/song.pls

Any way of doing this? So far, the only solution I have found would be to use the "ghetto" authentication scheme, build a user/ID into my application, and not distribute said user ID/password. In this way, anyone who tried to access the on-demand content directly would be prompted for an ID and password. I would rather use the masked/one-time-use url method, but if authentication is my only option, so be it.

Thanks!

[FesterHead]

Try using on-demand with a webserver along with some form of file permissions such as .htaccess.