Re: soup_message_io_pause and disconnects

[Dan Winship <danw gnome org>]

Sorry for the delay... I haven't had much time for libsoup hacking lately.

Victor Grishchenko wrote:
> Good day!
>
> I ran into the following problem: while a request is paused, the client
> disconnects, so I get
>
> (process:9347): libsoup-CRITICAL **: soup_socket_is_connected: assertion
> `SOUP_IS_SOCKET (sock)' failed
> (process:9347): libsoup-CRITICAL **: soup_socket_disconnect: assertion
> `SOUP_IS_SOCKET (sock)' failed
> 1185340379>=1185340385, kicking
> (process:9347): libsoup-CRITICAL **: soup_message_set_status: assertion
> `SOUP_IS_MESSAGE (msg)' failed
> (process:9347): GLib-GObject-WARNING **: instance of invalid
> non-instantiatable type `(null)'
> ./run++: line 5:  9347 Segmentation fault      (core dumped)
> LD_LIBRARY_PATH=/usr/lib:/home/gritzko/lib ./httpxmppgw
...
> So, what is the recommended way to listen to user's disconnects?

There's no way for the application to know when a socket has 
disconnected. Soup ought to be just doing the right thing on its own.

I've entered this bug into bugzilla: 
http://bugzilla.gnome.org/show_bug.cgi?id=471385. You can add yourself 
as a cc: if you want to be notified when it's fixed. (Not sure when that 
will be; there may not be a new libsoup release for GNOME 2.20.)

-- Dan