log libpurple/protocols/msn/directconn.c @ 30411:cd022bd83677

age author description
Thu, 03 Jun 2010 01:22:31 +0000 Mark Doliner I noticed that this wasn't being used
Fri, 28 May 2010 23:30:20 +0000 Elliott Sales de Andrade It's probably best just to be explicit about the ordering here.
Fri, 28 May 2010 21:26:57 +0000 Elliott Sales de Andrade For some reason, this line creates the following warning:
Wed, 26 May 2010 23:20:18 +0000 Elliott Sales de Andrade I think it's more accurate to say that a DC is a P2P transfer, so if that
Sun, 23 May 2010 21:45:19 +0000 Elliott Sales de Andrade NULL-ify some reverse links so that there's no double-free on exit.
Fri, 21 May 2010 07:43:18 +0000 Elliott Sales de Andrade C comments only.
Fri, 21 May 2010 07:36:59 +0000 Elliott Sales de Andrade Make it more explicit that incoming and outgoing timeouts are different.
Thu, 20 May 2010 09:06:47 +0000 Elliott Sales de Andrade If there's stuff stuck in the DC queue, then try to send it over the SB if
Mon, 17 May 2010 08:45:46 +0000 Elliott Sales de Andrade Ref the slplink before destroying the DC, or we might lose our slpcall.
Mon, 17 May 2010 08:42:51 +0000 Elliott Sales de Andrade Use msn_dc_fallback_to_p2p where possible.
Mon, 17 May 2010 07:56:00 +0000 Elliott Sales de Andrade This is not a timeout, but an input handler.
Mon, 17 May 2010 07:34:52 +0000 Elliott Sales de Andrade Fallback to P2P if connecting to external IP didn't work immediately.
Sat, 15 May 2010 08:02:08 +0000 Elliott Sales de Andrade If removing a timeout and return FALSE in its handler isn't good, then
Sat, 08 May 2010 00:08:01 +0000 Elliott Sales de Andrade We can't both remove a timeout and return FALSE in its callback.
Thu, 06 May 2010 07:36:56 +0000 Elliott Sales de Andrade This should probably work a bit better. At least, we want to get rid of any