Re: GUPnP client invocations and timeout

[Jens Georg <mail jensge org>]

On Mi, 2012-01-25 at 09:48 +0100, Branislav Katreniak wrote:

> When we don't ever touch result of
> gupnp_service_proxy_begin_action (reported in different thread),
> we have no need to fork (now).

I just noticed this different thread remark: GUPnP is _NOT_ threadsafe
at all. The only supported way to use it in a thread is to create a
dedicated GUPnP worker thread with its own GMainLoop and GMainContext
and do everything in that thread context.