Changeset 501b4e0 for protocols/jabber
- Timestamp:
- 2006-10-02T16:42:32Z (18 years ago)
- Branches:
- master
- Children:
- 995913b
- Parents:
- d9282b4
- Location:
- protocols/jabber
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
protocols/jabber/io.c
rd9282b4 r501b4e0 52 52 it via the event handler. If not, add the handler. (In 53 53 most cases it probably won't be necessary.) */ 54 /* Disabling this trick for now because there's really not 55 a good way to catch errors yet. :-( 54 56 if( jabber_write_callback( gc, jd->fd, GAIM_INPUT_WRITE ) ) 57 */ 55 58 jd->w_inpa = b_input_add( jd->fd, GAIM_INPUT_WRITE, jabber_write_callback, gc ); 56 59 } … … 64 67 } 65 68 66 /* FIXME: write_callback could've generated a real error! */ 69 /* FIXME: write_callback could've generated a real error! Have to 70 find a way to find out if we have to return 0 here. Looking for 71 ourselves in the linked list of connections is a possibility, 72 but it'd be too time-consuming... */ 67 73 return 1; 68 74 } -
protocols/jabber/sasl.c
rd9282b4 r501b4e0 64 64 if( !sup_plain && !sup_digest ) 65 65 { 66 hide_login_progress( gc, "No known SASL authentication schemes supported" ); 66 67 signoff( gc ); 67 68 return XT_ABORT;
Note: See TracChangeset
for help on using the changeset viewer.