soup-transcoding-proxy - Transcodes N HTTP streams and makes them available as new live HTTP streams to M clients

Age	Commit message (Collapse)	Author	Files	Lines
2014-07-11	clients: Fix increment of client timeout	Nirbheek Chauhan	1	-1/+1

2014-07-11	Add license headers and COPYING	Nirbheek Chauhan	1	-2/+21

2014-07-11	appsrc: Remove need-data/enough-data signal handlers	Nirbheek Chauhan	1	-24/+0
	Dead code. Signals were disabled, and using this and pausing the message causes problems with libsoup.
2014-07-10	appsink: Add a client timeout, and handle eos separately	Nirbheek Chauhan	1	-5/+40
	If no chunks are written to a client for 10 seconds, we end that stream and clean it up. This is currently happening due to a bug, but might happen due to bad/slow clients as well. Instead of handling EOS from null samples, handle EOS through the signal handler. This is a more reliable way of handling EOS, and also works when the whole pipeline is torn down because the PUT stream ended.
2014-07-10	debug: Use separate #ifdefs for each DEBUG	Nirbheek Chauhan	1	-3/+3

2014-07-09	appsink: Use a GMutex to control when we pull samples	Nirbheek Chauhan	1	-34/+28
	We can only pull a new sample and write it out if the previous one has been written, otherwise we get a segfault in SoupMessage.
2014-07-09	appsrc: Queue an EOS when aborted too	Nirbheek Chauhan	1	-0/+21

2014-07-09	appsink: Push samples when availability is signalled	Nirbheek Chauhan	1	-34/+16
	This is to demonstrate that this doesn't work. It seems that using the SoupMessage associated with a response outside the signal handler for which it was created can result in a segfault, and eventually does.
2014-07-09	main/appsink: Don't hard-code element names	Nirbheek Chauhan	1	-6/+4

2014-07-09	main: Add option parsing (port)	Nirbheek Chauhan	1	-3/+21

2014-07-09	Add source files	Nirbheek Chauhan	1	-0/+562