On Fri, Sep 25, 2015 at 10:01 AM, Ruediger Pluem <[email protected]> wrote: > > On 09/25/2015 09:27 AM, [email protected] wrote: >> >> URL: http://svn.apache.org/viewvc?rev=1705236&view=rev >> > > Can't we run in endless loops here, because no new input will arrive until > the output buffer was flushed (e.g. due to > pending SSL layer data the client is waiting for before it sents new data)? > Or do you expect the non blocking readers > to switch to blocking next time they read?
The idea was that the reader either expects data and blocks, or is just polling what's available now. But hm, event/motorz may not follow that scheme, and poll() the socket directly (w/o flushing) after some previous non-blocking read is EAGAIN. Flushing defeats pipelining, so maybe it's not achievable with SSL/TLS... Any other way around? Regards, Yann.
