> The code you say you added is already there, but after the > > WSocket_Synchronized_WSAASyncSelect call, so what needs to be understood > is > if this call, and the related in the finally section of the try > block, is > really needed when not in a SSL request, as the non-SSL > version of the > component doesn't call this WSAASyncSelect method, and > this inherited > Do_FD_READ(msg) is the only code that will be called in a > non-SSL situation > anyway.
And this is exactly the problem... calling WSocket_Synchronize_WSAAsyncSelect in Do_FD_READ when NOT in SSL.. by just adding the SSL socket to the inheritance of classe (Activating USE_SSL) will change the behavior or Do_FD_READ of NON SSL sockets.. and this screws our whole software and I bet it must screw other users as well. I have a theory that it might be only affecting sockets with Naggle disabled (which we do by default), but I have to test and confirm it (because nobody else reported this issue and it is a very very visible problem for us) I added that verification code BEFORE WSocket_Synchronize_WSAAsyncSelect so it won't be called if not in SSL, but apparently Angus did not like it... > The move of this WSocket_Synchronized_WSAASyncSelect calls to this > method, done in the V8.22, is about a fix in SSL, so I suppose this > "Fixed SSL bug where two consecutive requests from a client would leave > a server in a waiting state and not process any other requests" is not > needed in non-SSL requests? I agree that they must have added to fix some SSL problem, but that is causing issue for NON-SSL sockets... while on SSL it looks like it is working fine for us as well, but it screws the non-ssl sockets entirely for us. Eric -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
