After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 619633 - associate pending connections with specific messages
associate pending connections with specific messages
Status: RESOLVED FIXED
Product: libsoup
Classification: Core
Component: HTTP Transport
2.26.x
Other Linux
: Normal normal
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2010-05-25 16:34 UTC by Dan Winship
Modified: 2010-06-09 15:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dan Winship 2010-05-25 16:34:17 UTC
Currently libsoup goes to some effort to keep pending connections independent of messages. this is useful in some cases when servers are slow to accept new connections, because it means that if a message gets queued, and we start creating a new connection for it, but then an existing keep-alive connection gets freed up, we can just queue the message on that connection rather than continuing to wait for the new one.

However, it also sucks in various ways, including the fact that if a connection fails, we don't know which message we had started creating it for, so we end up cancelling all pending messages for that host, which is lame when the server or network is just slightly-flaky and, eg, drops every 10th connection.

It also makes the bookkeeping a lot more complicated, and makes it really difficult to answer the question "is this message currently blocked on DNS".

So, change that.
Comment 1 Dan Winship 2010-06-09 15:28:33 UTC
ok, this turned into a big yak-shaving mission (mostly because of the handling of https proxy CONNECT), but I've pushed this to master now. Everyone should update!