- 24 Feb, 2015 7 commits
-
-
Martin Storsjö authored
Many of these functions were named foo_free_context, and since the functions no longer should free the context itself, only allocated elements within it, the previous naming was slightly misleading. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This makes it more consistent with depacketizers that don't have any .free function at all, where the payload context is freed by the surrounding framework. Always free the context in the surrounding framework, having the individual depacketizers only free any data they've specifically allocated themselves. This is similar to how this works for demuxer/muxers/codecs - a component shouldn't free the priv_data that the framework has allocated for it. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This makes it clear that the individual parsing functions can't touch the parsed out value. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This avoids implementing a full function just to set this one field. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 22 Feb, 2015 1 commit
-
-
Thomas Volkert authored
(tested with live555 RTSP server) Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 21 Feb, 2015 1 commit
-
-
Thomas Volkert authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 15 Feb, 2015 1 commit
-
-
Thomas Volkert authored
Tested with live555 RTSP server Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-