https://bugs.winehq.org/show_bug.cgi?id=52769
--- Comment #5 from Nikolay Sivov bunglehead@gmail.com --- (In reply to yshuiv7 from comment #4)
(In reply to Nikolay Sivov from comment #2)
I don't think we should rely on gstreamer for this. We should have win32 based implementations for network bytestreams, and make that work with gstreamer source the same way file streams are working now.
This is my original plan for implementing http and https as well. But then I realized rtsp cannot be a bytestream, as it can have multiple separate audio/video streams. It has to be exposed as a media source. Using gstreamer's uridecodebin helps us easily cover as much protocols as possible.
It's normally a property of the container to provide multiple streams, not the protocol. Same as a disk file having one video and multiple audio streams, still exposed as a single bytestream. Is that somehow different for rtsp? Do you mean it's impossible to create a bytestream object for rtsp url at all?
Implementing rtsp from scratch would be a much larger undertaking, personally I think it would be good to have something working first, for the users that need this. But I can understand if the devs here object.
Starting with http/https is fine.