Searched refs:write_resp (Results 1 – 4 of 4) sorted by relevance
1688 if(data->conn->handler->write_resp) { in Curl_xfer_write_resp()1691 result = data->conn->handler->write_resp(data, buf, blen, is_eos, done); in Curl_xfer_write_resp()
821 CURLcode (*write_resp)(struct Curl_easy *data, const char *buf, size_t blen, member
100 o lib: replace readwrite with write_resp [137]
960 - lib: replace readwrite with write_resp979 + CURLcode (*write_resp)(struct Curl_easy *data, const char *buf, size_t ble999 The HTTP protocol handlers `write_resp()` implementation will get passed1029 `Curl_xfer_write_resp()`. It calls the protocol handler's `write_resp()`