Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
|
|
|