Jørgen Lind wrote:
Hi guys.
I have implemented a proposal for thread affinity for libwayland-client.
By this I mean that proxies belong to threads. So events will be
dispatched in the thread that created the proxy. Obviously proxies can
be moved between threads if that is desired.
As a side
Hi guys.
I have implemented a proposal for thread affinity for libwayland-client.
By this I mean that proxies belong to threads. So events will be
dispatched in the thread that created the proxy. Obviously proxies can
be moved between threads if that is desired.
As a side-effect I also
ive pretty odd behavior without this
patch.
I don't expect this patch to be picked up, so I added a define so that
the two added functions can safly be used with client code and
fixed error messages.
Jørgen
>From 24b8dccb2f48bc8595d40288106d51d3f4605544 Mon Sep 17 00:00:00 2001
From: =?UT
On 03/05/2012 01:14 PM, Jørgen Lind wrote:
> Hi,
>
> I had some time today update the patch to add thread affinity to
> wayland-clients wl_display.
>
Not that anyone else seem to have picked up this patch, but I've got
some small issues with it even so.
Code is copy-pasted
Hi,
I had some time today update the patch to add thread affinity to
wayland-clients wl_display.
Jørgen
>From eca8c247e18c66d691aa07fc16cbaa9ea1e5e843 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=B8rgen=20Lind?=
Date: Mon, 5 Mar 2012 12:44:37 +0100
Subject: [PATCH] Add thread affinity
Hi guys,
We have had a patch in Qt-Wayland since November that has given us some
thread affinity to Wayland clients so we can assure that we don't run
wl_display_iterate from other threads then the thread that actually created the
display. I have just cleaned it up a bit and was hoping to g
