Changeset 29ff5c2 for protocols/jabber/s5bytestream.c
- Timestamp:
- 2015-11-21T00:01:50Z (8 years ago)
- Parents:
- e4f08bf (diff), 8fdeaa5 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
protocols/jabber/s5bytestream.c
re4f08bf r29ff5c2 85 85 return jabber_bs_abort(bt, msg ": %s", strerror(errno)); } 86 86 87 gboolean jabber_bs_abort(struct bs_transfer *bt, char *format, ...) ;87 gboolean jabber_bs_abort(struct bs_transfer *bt, char *format, ...) G_GNUC_PRINTF(2, 3); 88 88 void jabber_bs_canceled(file_transfer_t *ft, char *reason); 89 89 void jabber_bs_free_transfer(file_transfer_t *ft); … … 536 536 * that sends atyp=0 addrlen=0 and only 6 bytes (one less than one would expect). 537 537 * Therefore I removed the wait for more bytes. Since we don't care about what else the proxy 538 * is sending, it should nt matter */538 * is sending, it should not matter */ 539 539 540 540 if (bt->tf->ft->sending) { … … 559 559 * An intelligent sender would probably specify himself as the first streamhost and 560 560 * a proxy as the second (Kopete and PSI are examples here). That way, a (potentially) 561 * slow proxy is only used if nec cessary. This of course also means, that the timeout561 * slow proxy is only used if necessary. This of course also means, that the timeout 562 562 * per streamhost should be kept short. If one or two firewalled adresses are specified, 563 563 * they have to timeout first before a proxy is tried.
Note: See TracChangeset
for help on using the changeset viewer.