Bug 25001

Summary:	Time out connection process after a minute (or so)
Product:	Wocky	Reporter:	Will Thompson <will>
Component:	General	Assignee:	Sjoerd Simons <sjoerd>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:	24353
Bug Blocks:

Description Will Thompson 2009-11-09 10:37:12 UTC

+++ This bug was initially created as a clone of Bug #24353 +++

Wocky should probably give up after a while if the connection process isn't going anywhere.

Gabble does this in 0.8, but not in 0.9 because I think the XMPP library should do it.

Comment 1 Nicolas Dufresne 2010-09-23 11:47:19 UTC

One option would be to use new GLib method g_socket_set_timeout(). The GSocket object can be retrieved from the GSocketConnection.

Second option would be to do nothing and let Gabble use a GCancellable along with g_timeout_add().

Any preferences ?

Comment 2 Will Thompson 2010-11-20 05:42:52 UTC

> One option would be to use new GLib method g_socket_set_timeout(). The GSocket
> object can be retrieved from the GSocketConnection.

Unfortunately this isn't enough for some cases. I've seen captive portals that "accept" the XMPP connection, happily read the data we send, and drop it on the floor. So we need to use a higher-level timeout.

> Second option would be to do nothing and let Gabble use a GCancellable along
> with g_timeout_add().

I think the library should do this, particularly since it's made more complicated by our support for interactive authentication...

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.