On Sat, Dec 12, 2009 at 4:12 PM, David Schwartz <dav...@webmaster.com> wrote: > Sebastian Treu wrote: > >> Well, maybe I miss the point of what man pages wanted to say with: >> >> "[...] >> WARNING >> When an SSL_write() operation has to be repeated because of >> SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE, it must be repeated >> with >> the same arguments. >> [...]" > > If you set ALLOW_MOVING_WRITE_BUFFER, the restriction is relaxed. The only > restriction that remains is that you must present a consistent data stream. > For example, if you try to SSL_write "foo" and two bytes are sent, your next > SSL_write *must* start with an "o".
That was the key then. I used the one in the man page: SSL_MODE_ENABLE_PARTIAL_WRITE but this writes 16kb _always_. I don't saw that option in the SSL_write() but I can see it on SSL_CTX_set_mode(). With this option set I don't get anymore WANT_WRITE when the client reads _partially_ and this let me _know_ more things to control the application flow. Thanks David for your time and the detailed answers about it. I promised not to bother the list anymore with SSL I/Os (*sic* at least I hope), -- If you want freedom, compile the source. Get gentoo. Sebastián Treu http://labombiya.com.ar ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
