Commit 1a991548 authored by Ignacio Casal Quinteiro's avatar Ignacio Casal Quinteiro Committed by Philip Withnall

gpollableoutputstream: document side effects of WOULD_BLOCK on D/TLS

If the underlying transport is D/TLS the same data and data length
is required to be sent on the next iteration when a WOULD_BLOCK
happens. This is due to the fact that gnutls or openssl keep
an internal state for the data.
parent 4752d72a
......@@ -178,6 +178,9 @@ g_pollable_output_stream_default_write_nonblocking (GPollableOutputStream *stre
* may happen if you call this method after a source triggers due
* to having been cancelled.
* Also note that if %G_IO_ERROR_WOULD_BLOCK is returned some underlying
* transports like D/TLS require that you send the same @buffer and @count.
* Virtual: write_nonblocking
* Returns: the number of bytes written, or -1 on error (including
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment