In that we had implemented multiple threads. Earlier we have implemented logic such as we have keep thread in sleep until the whole video not recorded completely and due to that reason recording process for recording video is getting delayed and we are not able to record from the end time of first video. So, to resolve this issue we have keep thread in sleep for the time of video length instead of waiting for the complete first video recording process.
For restrict user from getting video URL we have implemented reverse proxy server which will first authenticate user request for play video and if request is valid then only it will communicate to nimble server and revert back the response to the flow player. For validating request we have created unique token and pass the token with every video URL, and if token is matched with database token, then the request will consider as valid otherwise it is invalid and proxy server will return access denied to the flow player
We have downloaded nimble setup for windows first and installed it, after installation nimble had created configuration files in its config directory. We need to setup nimble configuration without subscription of WMS panel, so for that we did research it on Google and found sample rules configuration. After that we have setup nimble rules config folder and map vod folder on that file. We need to setup nimble configuration in nimble config file, first step is we must specify nimble service port, default will be 8081 you may change it later on. For setting up SSL with nimble we need to specify nimble SSL port in nimble config file, you must specify certificate file path and key for that file.