1. How would I segment the VOD based on accounts. For example…if I have 300 unique customers publishing their streams to my server, I want their streams to be recorded and saved to their own folders so that only their streams can be accessed in a playlist.
The easiest way to do this would be to use Stream Aliasing to protect the content and then just record to folders for each of your customers. You can then provide selective access to that content for each of your customers by creating aliases (via addStreamAlias) for any file they want to access.
To completely silo your customers you can do Virtual Hosting, which is essentially just running the EMS multiple times on your computer/server. This requires setting up a new config.lua file (using different listen ports) for each of the instances you want to create.
Someone wrote:
2. How are the VOD files named. Is this something that evostream does automatically. What if I want the individual customer to be able to name his / her own videos.
When you record, you specify a pathToFile parameter, this must include the file name along with the directory path.
Someone wrote:
3. Is there someway to publish the contents of all files in a folder someway…maybe XML, so that it can be accessed by a video players, such as iw player for viewing.
Unfortunatly no.
Someone wrote:
4. Basically what I am trying to accomplish is a ustream, or live stream type service…just smaller and more specialized.
We have many clients that use our software to host live video sharing services, so this is a great fit! Per #3 above, the EMS is not intended to be a vod/content-management tool, it is a Media Streaming Server. There are lots of things you can do from a vod/content-management perspective with the EMS and a simple web server like Apache. It does, however, typically require users to take advantage of our web services to create their custom business logic.