based Stream Suffix Generation in RTSP2WS
Hello, thank you for your project. It's extremely helpful. Here's our application scenario: Our service program generates the final stream suffixes based on user requests. These suffixes follow a pattern and fall within a certain range. So, we've pre - configured all possible suffixes in the config.json file according to this pattern. When a user requests the service, the dynamically generated suffix is guaranteed to be in the config.json file, enabling the user to preview the video.
However, there's a problem. With 1000 lines of configuration, the service consumes all available resources as soon as it starts.
Is it possible to add an option? If this option is enabled, rtsp2ws won't process the config.json file immediately. Instead, it will parse the corresponding address in the config.json file and retrieve the stream only when a user makes a request. Wouldn't this reduce resource consumption?
Alternatively, we could start an rtsp2ws process each time a stream suffix is generated. But wouldn't this lead to port conflicts?
1 条评论