Build script for creating persistent streams

[hburgund]

There are numerous situations where it is is required to have a dynamically generated and therefore flexible and evolving RW stream that is persistent without a specific client. Out of range streams and demo streams are two obvious examples, but there are other use cases as well.

This feature should have a web UI to make it easy to use; perhaps the best idea is to have it be part of the new web admin?

Features must include:

• generate stream for specified session
• update stream with tag filters
• update stream with location
• keep stream alive with heartbeat
• periodically verify if stream is alive and restart if not
• kill stream on demand

related to #95

[hburgund]

there seems to be some kind of memory leak for streams as those that exist for a while take more and more RAM until they crash. Since server-side streaming isn't the long-term goal, the best solution is probably to have the script that generates and persists the stream also kill and re-generate the stream after a set period of time has passed, say one day.

I think having a streams/:id/kill/ endpoint would be helpful for this and other reasons. Will investigate. #363 #364

[hburgund]

with client-side mixing happening, this becomes less important.