Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
aa7c88df
Commit
aa7c88df
authored
Sep 13, 2012
by
Andrey Utkin
Committed by
Michael Niedermayer
Sep 15, 2012
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document tcp proto 'timeout' parameter behavior
Signed-off-by:
Michael Niedermayer
<
michaelni@gmx.at
>
parent
a9e48177
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
0 deletions
+5
-0
protocols.texi
doc/protocols.texi
+5
-0
No files found.
doc/protocols.texi
View file @
aa7c88df
...
@@ -578,6 +578,11 @@ tcp://@var{hostname}:@var{port}[?@var{options}]
...
@@ -578,6 +578,11 @@ tcp://@var{hostname}:@var{port}[?@var{options}]
@item listen
@item listen
Listen for an incoming connection
Listen for an incoming connection
@item timeout=@var{microseconds}
In read mode: if no data arrived in more than this time interval, raise error.
In write mode: if socket cannot be written in more than this time interval, raise error.
This also sets timeout on TCP connection establishing.
@example
@example
ffmpeg -i @var{input} -f @var{format} tcp://@var{hostname}:@var{port}?listen
ffmpeg -i @var{input} -f @var{format} tcp://@var{hostname}:@var{port}?listen
ffplay tcp://@var{hostname}:@var{port}
ffplay tcp://@var{hostname}:@var{port}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment