On Thu, 14 Jun 2012, Diego Biurrun wrote:
---
I'm not entirely sure this is fully correct as I'm not sure if things like
"concat" should be mentioned in this list. Also, for some protocols (HLS?)
mentioning the long name instead of the abbreviation might be better.
doc/general.texi | 18 +++++++++++++++++-
1 files changed, 17 insertions(+), 1 deletions(-)
diff --git a/doc/general.texi b/doc/general.texi
index dee8f9e..d8adc0e 100644
--- a/doc/general.texi
+++ b/doc/general.texi
@@ -805,18 +805,34 @@ performance on systems without hardware floating point
support).
@multitable @columnfractions .4 .1
@item Name @tab Support
@item Apple HTTP Live Streaming @tab X
+@item concat @tab X
+@item crypto @tab X
@item file @tab X
@item Gopher @tab X
+@item HLS @tab X
@item HTTP @tab X
-@item MMS @tab X
+@item HTTPPROXY @tab X
+@item HTTPS @tab X
+@item MD5 @tab X
+@item MMSH @tab X
+@item MMST @tab X
@item pipe @tab X
+@item RTMP @tab X
+@item RTMPE @tab E
+@item RTMPS @tab E
+@item RTMPT @tab E
+@item RTMPTE @tab E
@item RTP @tab X
+@item SCTP @tab X
@item TCP @tab X
+@item TLS @tab X
@item UDP @tab X
@end multitable
I'm not sure if it's useful to list every single one of them - e.g.
httpproxy is more or less an internal detail - it's for creating a plain
connection via a http proxy, which you'd normally just use as a
implementation detail internally when connecting tls (or https) via a
proxy. But in some very special cases you could want to use it directly,
too. The rtmphttp protocol in Samuel's patch is the same but with even
less reason for anyone to ever use it directly.
Or put another way - this list is probably most useful for a user
wondering "does libav support protocol X?", and such a user won't really
know about our own internal protocols.
HLS is already listed as Apple HTTP Live Streaming.
// Martin
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
