On Tue, Jan 25, 2011 at 4:02 PM, Zan Dobersek wrote:
> Thanks for the reply.
> The following is what pushed me into researching the problem - I've created
> a test application that sets up a display and tries to create a client that
> connects to that display, but the client does not connect.
> Ju
Thanks for the reply.
The following is what pushed me into researching the problem - I've created
a test application that sets up a display and tries to create a client that
connects to that display, but the client does not connect.
Just as in compositor, I create a wl_display, add a socket to it
You have it right.
When a client does a connect on a socket that another process is listening to
(the listen is at line 692), this makes the other end get a "readable" on its
end of the socket. You then do an accept, which gives you a new fd for your
end of the connection. You then have a bid
Greetings,
I'm wondering what exactly sets off the socket_data function in
wayland/wayland-server.c at approximate line 640. I can see that we add a
file descriptor object of our socket to the main loop in
wl_display_add_socket that uses socket_data as the callback function when a
client connects
