If you want *really* easy to set up for static files, try thttpd!

The bit where the webserver sends a small static file is almost irrelevant!

That is, when they're not in use, this will go and infect the static file.

A web server serving static files could be written in JavaScript like this:

So you compress it to this static file which at some point later you're going to decompress.

Serving static files on a webserver to multiple users at once.

As mentioned before, the UVC-based approach has only been effectively implemented for static files.

The issue with the static files also bugs me.

The web server handles static files: content, and the playlist(s).

Why check on static files if not to see whether somebody else has accessed them?