• Kristian H. Kristensen's avatar
    Split the global registry into its own wl_registry object · 9fe75537
    Kristian H. Kristensen authored
    The only way to make the global object listener interface thread safe is to
    make it its own interface and make different listeners different wl_proxies.
    The core of the problem is the callback we do when a global show up or
    disappears, which we can't do with a lock held.  On the other hand we can't
    iterate the global list or the listener list without a lock held as new
    globals or listeners may come and go during the iteration.
    Making a copy of the list under the lock and then iterating after dropping
    the lock wont work either.  In case of the listener list, once we drop the
    lock another thread may unregister a listener and destroy the callbackk
    data, which means that when we eventually call that listener we'll pass it
    free memory and break everything.
    We did already solve the thread-safe callback problem, however.  It's what
    we do for all protocol events.  So we can just make the global registry
    functionality its own new interface and give each thread its own proxy.
    That way, the thread will do its own callbacks (with no locks held) and
    destroy the proxy when it's no longer interested in wl_registry events.
Last commit
Last update
.gitignore Loading commit data...
Makefile.am Loading commit data...
protocol.xsl Loading commit data...
wayland-protocol.css Loading commit data...
wayland.xml Loading commit data...