> You are doing everything except trying to understand that your > knowlage about something has changed comes from windows, and > windows notifies you about it in special cases. It is possible > that something will change and windows won't notify you. You have > to know about it before you block in wait function.
It's only possible for something to change and Windows not to notify you if that wasn't the thing you were waiting for. > Windows sends FD_WRITE event if writing is possible and previous > invokation of 'send' has failed with WSAEWOULDBLOCK code (only > this code, if it has failed from other reason, FD_WRITE will not > be send and waiting for it will cause deadlock)... If the previous operation didn't fail because a write wasn't possible, why would you care if a write was possible? > What words should i use, you will understand this?! Nevermind, i > cut this thread ,forget about everything, this is my last post, > don't answer to it... I give up. I don't know how I can make it clearer. If an OpenSSL operation fails, there are only two possibilities: 1) It was because a write wasn't possible, in which case you will get an FD_WRITE notification. 2) It wasn't because a write wasn't possible, in which case even if you got an FD_WRITE notification, it wouldn't indicate anything had changed, so the operation would still fail. Perhaps someone else can say it more clearly. DS ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
