Apologies if this is a duplicate; I was messing around with my e-mail
yesterday and it was broken for a while. I didn't see this go through.
On Sun, Aug 20, 2006 at 06:54:36PM -0400, Joe Flowers wrote:
> It means call exactly the same SSL function you just did with the exact
> same parameters as you just did that produced this SSL_ERROR_WANT_WRITE
> return.
Pardon me, I think I'm a little thick today. I get what you're
all saying but I'm still not 100% sure of how this should be applied.
Here's the program flow, without SSL:
while(!quit) {
for(i in all file descriptors) {
if(we have something buffered up to say to the server)
FD_SET(thisfd, &writefds)
/* we are always interested in what the server has to say
* to us */
FD_SET(thisfd, &readfds);
}
select(maxfd + 1, &readfds, &writefds, NULL, timeout);
if(FD_ISSET(thisfd, &readfds)) {
read(thisfd), process it, probably send a reply with write()
} else if(FD_ISSET(thisfd, &writefds) {
write(thisfd) whatever we have buffered up; if it was a partial
write, update the buffer.
}
}
Using SSL, how should this look? From what I'm hearing, it shouldn't
use select() at all. So how do I find out if the server has something
to say short of polling it with SSL_read?
Thanks,
Steve.
----- End forwarded message -----
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
