You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have encountered a situation that requires using a slash ("/") in an AppName, such as "live/0", and I'm curious about its feasibility within Livego. My interest arose while examining the code, particularly at this point in the HLS module, where I suspect the issue I'm facing originates.
Can Livego support an AppName with a slash ("/"), specifically names like "live/0"? If this is not supported, is there an alternative approach to achieve a hierarchical naming system for streams?
Given the code segment mentioned, are there any modifications or configurations I can apply to bypass or mitigate this limitation?
What are the implications or potential issues of attempting to use a slash ("/") in an AppName, based on Livego's current implementation?
The hierarchical naming convention is crucial for the structure and organization of my project, and understanding whether Livego can accommodate this format directly affects my planning and development process.
The text was updated successfully, but these errors were encountered:
I have encountered a situation that requires using a slash ("/") in an AppName, such as "live/0", and I'm curious about its feasibility within Livego. My interest arose while examining the code, particularly at this point in the HLS module, where I suspect the issue I'm facing originates.
Can Livego support an AppName with a slash ("/"), specifically names like "live/0"? If this is not supported, is there an alternative approach to achieve a hierarchical naming system for streams?
Given the code segment mentioned, are there any modifications or configurations I can apply to bypass or mitigate this limitation?
What are the implications or potential issues of attempting to use a slash ("/") in an AppName, based on Livego's current implementation?
The hierarchical naming convention is crucial for the structure and organization of my project, and understanding whether Livego can accommodate this format directly affects my planning and development process.
The text was updated successfully, but these errors were encountered: