Since all URLContexts have the same AVOptions, such AVOptions
will be applied on the outermost context only and removed from the
dict, while they probably make sense on all contexts.
This makes sure that rw_timeout gets propagated to the innermost
URLContext (to make sure it gets passed to the tcp
On Sat, 19 Mar 2016, Martin Storsjö wrote:
Since all URLContexts have the same AVOptions, such AVOptions
will be applied on the outermost context only and removed from the
dict, while they probably make sense on all contexts.
This makes sure that rw_timeout gets propagated to the innermost
URLC
Since all URLContexts have the same AVOptions, such AVOptions
will be applied on the outermost context only and removed from the
dict, while they probably make sense on all contexts.
This makes sure that rw_timeout gets propagated to the innermost
URLContext (to make sure it gets passed to the tcp
On Sat, 19 Mar 2016, Anton Khirnov wrote:
Quoting Martin Storsjö (2016-03-18 13:01:40)
Since all URLContexts have the same AVOptions, such AVOptions
will be applied on the outermost context only and removed from the
dict, while they probably make sense on all contexts.
This makes sure that rw_
Quoting Martin Storsjö (2016-03-18 13:01:40)
> Since all URLContexts have the same AVOptions, such AVOptions
> will be applied on the outermost context only and removed from the
> dict, while they probably make sense on all contexts.
>
> This makes sure that rw_timeout gets propagated to the inner
On 18/03/16 13:01, Martin Storsjö wrote:
> Suggestions on how to do this better are welcome.
We could add flags to the options and have a consume mode that drops the
options as they are found and a preserve mode that does not as alternative.
lu
___
liba
