If shutdown_read is TRUE then the receiving side of the connection is shut
down, and further reading is disallowed. Subsequent calls to
g_datagram_based_receive_messages() will return G_IO_ERROR_CLOSED.
If shutdown_write is TRUE then the sending side of the connection is shut
down, and further writing is disallowed. Subsequent calls to
g_datagram_based_send_messages() will return G_IO_ERROR_CLOSED.
It is allowed for both shutdown_read and shutdown_write to be TRUE — this
is equivalent to calling g_dtls_connection_close().
If cancellable is cancelled, the GDtlsConnection may be left
partially-closed and any pending untransmitted data may be lost. Call
g_dtls_connection_shutdown() again to complete closing the GDtlsConnection
Shut down part or all of a DTLS connection.
If shutdown_read is TRUE then the receiving side of the connection is shut down, and further reading is disallowed. Subsequent calls to g_datagram_based_receive_messages() will return G_IO_ERROR_CLOSED.
If shutdown_write is TRUE then the sending side of the connection is shut down, and further writing is disallowed. Subsequent calls to g_datagram_based_send_messages() will return G_IO_ERROR_CLOSED.
It is allowed for both shutdown_read and shutdown_write to be TRUE — this is equivalent to calling g_dtls_connection_close().
If cancellable is cancelled, the GDtlsConnection may be left partially-closed and any pending untransmitted data may be lost. Call g_dtls_connection_shutdown() again to complete closing the GDtlsConnection