.\" Automatically generated man page, do not edit .TH QB_IPCC_GET_BUFFER_SIZE 3 2020-10-31 "LIBQB" "libqb Programmer's Manual" .SH NAME qb_ipcc_get_buffer_size \- What is the actual buffer size used after the connection. .SH SYNOPSIS .nf .B #include .sp \fBint32_t qb_ipcc_get_buffer_size\fP( \fBqb_ipcc_connection_t *\fP\fIc\fP ); .fi .SH PARAMS \fBc \fP\fIconnection instance \fP .PP .SH DESCRIPTION .RE \fBconnection \fPsize in bytes or -error code .PP .SH NOTE .PP The buffer size is guaranteed to be at least the size of the value given in qb_ipcc_connect, but it is possible the server will enforce a larger size depending on the implementation. If the server side is known to enforce a buffer size, use this function after the client connection is established to retrieve the buffer size in use. It is important for the client side to know the buffer size in use so the client can successfully retrieve large server events. .SH SEE ALSO .PP .nh .ad l \fIqb_ipcc_send\fR(3), \fIqb_ipcc_sendv_recv\fR(3), \fIqb_ipcc_recv\fR(3), \fIqb_ipcc_event_recv\fR(3), \fIqb_ipcc_fc_enable_max_set\fR(3), \fIqb_ipcc_is_connected\fR(3), \fIqb_ipcc_sendv\fR(3), \fIqb_ipcc_context_set\fR(3), \fIqb_ipcc_context_get\fR(3), \fIqb_ipcc_verify_dgram_max_msg_size\fR(3), \fIqb_ipcc_connect\fR(3), \fIqb_ipcc_disconnect\fR(3), \fIqb_ipcc_fd_get\fR(3) .ad .hy .SH "COPYRIGHT" .PP Copyright (C) 2010-2020 Red Hat, Inc. All rights reserved.