aboutsummaryrefslogtreecommitdiffstats
path: root/HACKING
diff options
context:
space:
mode:
authorDan Winship <danw@src.gnome.org>2001-09-26 05:14:09 +0800
committerDan Winship <danw@src.gnome.org>2001-09-26 05:14:09 +0800
commit4f83aaa7cc34a880c7fc2332bcb6cd36b0b01a08 (patch)
treee14e9dc7890dd156f444ed84eeba28d5db07a178 /HACKING
parent3c4c88c9741faaa1e3d466fb1458dd4f212b42eb (diff)
downloadgsoc2013-evolution-4f83aaa7cc34a880c7fc2332bcb6cd36b0b01a08.tar
gsoc2013-evolution-4f83aaa7cc34a880c7fc2332bcb6cd36b0b01a08.tar.gz
gsoc2013-evolution-4f83aaa7cc34a880c7fc2332bcb6cd36b0b01a08.tar.bz2
gsoc2013-evolution-4f83aaa7cc34a880c7fc2332bcb6cd36b0b01a08.tar.lz
gsoc2013-evolution-4f83aaa7cc34a880c7fc2332bcb6cd36b0b01a08.tar.xz
gsoc2013-evolution-4f83aaa7cc34a880c7fc2332bcb6cd36b0b01a08.tar.zst
gsoc2013-evolution-4f83aaa7cc34a880c7fc2332bcb6cd36b0b01a08.zip
call SSL_read/write, looping on SSL_ERROR_WANT_READ/WRITE. I'm sure
* camel-tcp-stream-openssl.c (my_SSL_read, my_SSL_write): call SSL_read/write, looping on SSL_ERROR_WANT_READ/WRITE. I'm sure there's a perfectly good reason that the API works this way. No, really. (stream_read, stream_write): use my_SSL_read and my_SSL_write. Fixes at least ximian 8593, and probably 6024 and maybe 10366, at least for OpenSSL. There may be a parallel NSS bug? svn path=/trunk/; revision=13121
Diffstat (limited to 'HACKING')
0 files changed, 0 insertions, 0 deletions