eldritch horrors
4ae6fb5a8f
don't pause the entire curl thread. we have multiple consumer threads
after all, not just one, so stalling all of them is likely not great.
note that libcurl advises against using transfer pauses if compressed
encodings are allowed and automatically decoded. this should not lead
to problems in practice because our data is usually not compressed to
such a degree that curl buffering *uncompressed* data matters. should
this cause problems we can reintroduce the whole-thread pause, but we
will probably get away with this until the entire file transfer class
is made kj::Promise-using async (and *then* curl can be hardpaused if
it cannot get rid of its data, solving the problem once and for all).
Change-Id:
|
||
|---|---|---|
| .. | ||
| data | ||
| common-protocol.cc | ||
| derivation.cc | ||
| derived-path.cc | ||
| downstream-placeholder.cc | ||
| filetransfer.cc | ||
| machines.cc | ||
| nar-info-disk-cache.cc | ||
| outputs-spec.cc | ||
| path.cc | ||
| protocol.hh | ||
| references.cc | ||
| serve-protocol.cc | ||
| worker-protocol.cc | ||