- Timestamp:
- 2008-02-17T12:34:47Z (17 years ago)
- Branches:
- master
- Children:
- 2625d6d
- Parents:
- 1ba7e8f
- Location:
- protocols
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
protocols/ft.h
r1ba7e8f r506e61b 48 48 * methods are zero-initialized. Instances will automatically be deleted once the transfer is completed, 49 49 * canceled, or the connection to the irc client has been lost (note that also if only the irc connection 50 * and not the dccconnection is lost, the file transfer will still be canceled and freed).50 * and not the file transfer connection is lost, the file transfer will still be canceled and freed). 51 51 * 52 52 * The following (poor ascii-art) diagram illustrates what methods are called for which status-changes: … … 160 160 161 161 /* 162 * This starts a file transfer from bitlbee to the user (currently via DCC).162 * This starts a file transfer from bitlbee to the user. 163 163 */ 164 164 file_transfer_t *imcb_file_send_start( struct im_connection *ic, char *user_nick, char *file_name, size_t file_size ); -
protocols/jabber/si.c
r1ba7e8f r506e61b 212 212 imcb_log( ic, "File transfer request from %s for %s (%zd kb). ", xt_find_attr( node, "from" ), name, size/1024 ); 213 213 214 imcb_log( ic, "Accept the DCCtransfer if you'd like the file. If you don't, issue the 'transfers reject' command.");214 imcb_log( ic, "Accept the file transfer if you'd like the file. If you don't, issue the 'transfers reject' command."); 215 215 216 216 tf = g_new0( struct jabber_transfer, 1 );
Note: See TracChangeset
for help on using the changeset viewer.