Feature request for stransmit: use separate URI notation for stdio about srt HOT 7 OPEN

I have a bad feeling about this :). The trick here is that the file: scheme is standardized, whereas pipe: isn't. I know, srt: isn't standardized either, but in this case it's our specific protocol, only to be widespread, whereas pipes are used everywhere in the world. Not sure how others are using pipes if this needs to be specified in the URI, but I haven't found anyone using pipe: scheme and all searches redirect me to file://.

One extra problem with pipe:5 is that UriParser will parse it as scheme="" host="pipe" port="5". The application still can distinguish it as a special case, but it's kinda clumsy.

In stransmit I simply used the standard file scheme with con as a special-case host specification, in which the path part isn't used. If this is about providing ability to use other descriptors than default 0 and 1, I think it should be possible to simply add support for this within the current specification, where the descriptor would be extracted from the path part in the URI - for example: file://con/5.

(Note that may be nonportable - in stransmit there's currently used cin and cout directly - see ConsoleSource and ConsoleTarget classes. There's no portable way to use any "numeric file descriptor" in standard C++, so this would have to be probably a POSIX-only feature.)

Note that I haven't tested using file:///dev/stdin as source, nor did I experiment with file:///proc/self/fd/... :)

from srt.

The only use of a pipe: URI being used that I'm familiar with is within ffmpeg. But that project has quite a few custom URIs for all the protocols and IO devices it supports.

Documantation
Pipe Class

from srt.

Well, would be nice to have some standard for pipes, however it better be portable and coexist with some other standards - and just using 0 1 and 2 is already POSIX-specific.

from srt.

How would UriParser parse
pipe://./#5

If I understand the URI spec correctly it should be
scheme="pipe" host="localhost" path="/" fragment="5"

Where you could then use the fragment to specify the fd on a POSIX system and win32 could just ignore the fragment

from srt.

Though I'm not sure authority is really needed. It might work just as well with pipe:/#5

from srt.

from srt.

Need some clear statement as to whether "pipe://5" or "pipe://#5" form is worth adding.

from srt.