[PATCH 3/3] client: Change the way fd's are buffered and flushed

2018-09-07 Thread Lloyd Pique
ffers, one messasge is sent -- it just might have unused fd's. To keep things sane, an explicit limit to the number of fd's per message is introduced of three. An error will be generated if there are more. Signed-off-by: Lloyd Pique --- src/connection.c| 93 +++

[PATCH 2/3] client: Add wl_display_soft_flush()

2018-09-07 Thread Lloyd Pique
return an EAGAIN, which would normally set a fatal display error if the core-client tried to do an internal flush if the output buffer became completely full. Signed-off-by: Lloyd Pique --- src/connection.c | 30 ++- src/wayland-client-core.h | 3 ++ src/wayland-client.c

Re: [PATCH] client: Allow send error recovery without an abort

2018-06-19 Thread Lloyd Pique
Hi Pekka, On Tue, Jun 19, 2018 at 5:12 AM Pekka Paalanen wrote: > I think the aim should be to remove the abort(). I do not see any > reason to leave it in even as an option. > Thank you. Will proceeed in that direction. > The soft-buffer in libwayland-client is quite small, the kernel socket

Re: [PATCH] client: Allow send error recovery without an abort

2018-06-18 Thread Lloyd Pique
I did. Thanks! - Lloyd On Mon, Jun 18, 2018 at 4:58 AM Pekka Paalanen wrote: > On Tue, 5 Jun 2018 18:14:54 -0700 > Lloyd Pique wrote: > > > Introduce a new call wl_display_set_error_handler_client(), which allows > > a client to register a callback function which is invoke