cpw.malu.xmpp.jingle_ft: 0cbefa74: It's not nessesary to store the xfer in ...

[malu at pidgin.im]

-----------------------------------------------------------------
Revision: 0cbefa74b91f62f94ea75878e4672bdcee2265a0
Ancestor: c427f44f6fce96050d95c9cd4ad1c56dec9c1c13
Author: malu at pidgin.im
Date: 2009-03-18T21:57:20
Branch: im.pidgin.cpw.malu.xmpp.jingle_ft
URL: http://d.pidgin.im/viewmtn/revision/info/0cbefa74b91f62f94ea75878e4672bdcee2265a0

Modified files:
        libpurple/protocols/jabber/jingle/file-transfer.c

ChangeLog: 

It's not nessesary to store the xfer in the JabberStream, since that is only
done in si.c, to lookup transfers for streamhost parsing.
Here we use the Jingle framework to keep stuff together

-------------- next part --------------
============================================================
--- libpurple/protocols/jabber/jingle/file-transfer.c	ae854ddf770634344f3810abc6d4f73aef8b241f
+++ libpurple/protocols/jabber/jingle/file-transfer.c	cea21182f747218a0f18f0b868c94e72116498e0
@@ -631,8 +631,6 @@ jingle_file_transfer_new_xfer(PurpleConn
 		purple_xfer_set_cancel_send_fnc(xfer, jingle_file_transfer_cancel_send);
 		purple_xfer_set_end_fnc(xfer, jingle_file_transfer_xfer_end);
 
-		js->file_transfers = g_list_append(js->file_transfers, xfer);
-
 		g_free(jid);
 		g_free(me);
 	}