On Sat, Dec 12, 2009 at 7:19 AM, Sebastián Treu <sebastian.t...@gmail.com> wrote: > differents arguments. I also noted that SSL_write() is "clever" enough > to send _any_ length, so segmented writes will be overriding that > warning (if I undestood what man wanted to say). When I say clever > enough, I meant that in what I have proven (e.g. sending a 3mb file) > SSL_write() sends it by it's own (yielding want_write until it finish > with buffered data). The main reason the solution was discarted is > because that warning on man pages.
I want to be clear with this. Re-reading it I fall that maybe someone could missunderstood it. What I wanted to say is that until the client did not finish reading all the "chunk" of data, SSL_write() will keep yielding WANT_WRITE. But, meanwhile we don't know how many data the client has fetched. Imagine the client decides to read chunk of Xbytes. Until the client did not read all the bytes that SSL_write() writes, we'll get WANT_WRITE without any notions on how many bytes have been read. So, in a given instant of time t0, we don't know if the WANT_WRITE is actually a client reading by chunks less than we are sending, or the client isn't reading at all. There is where it should appears select(). Am I wrong? Regards, -- 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
