Re: GUPnP client invocations and timeout

[Sven Neumann <s neumann raumfeld com>]

On Tue, 2012-01-24 at 19:47 +0100, Jens Georg wrote:
> Hi,
> 
> thank you for your patch, but SoupSession has a "timeout" property which
> is by default set to "0" (infinite). If the timeout occurs the message
> will be finished with SOUP_STATUS_IO_ERROR. Despite the description this
> also works on the SessionAsync we use in GUPnP. With regards to wakeups
> I'd prefer to use that instead of an extra timer.

Does that timeout property really work for you? Last I tried (which is
admittedly quite a while), this didn't work. And as you said, the
document implies that it would only affect synchronous soup sessions.


Sven