> I call it like this, the only event that is called is SslShutDownComplete
> which
> sets FSSLShutdownComplete property, I don't have any other event
> processing here
>
> FSocket.Shutdown(SD_BOTH);
>
> EndTime := GetTickCount + FTimeout;
> while {$IFDEF USE_SSL} not FSSLShutdownComplete {$ELSE} False {$ENDIF} do
> begin
> if GetTickCount > EndTime then
> break;
> Sleep(10);
> FSocket.ProcessMessages;
> end;
>I don't know from where this code is called, but it CANNOT be called from an
>event handler originating from TWSocket.
>ProcessMessage is actually calling the window procedure for all windows
>created in the thread context and in turn trigger events at the component
>level. If any event hanlder is blocking, the ProcessMessages looks blocking.
>Calling Synchronize will actually block the thread until the main thread has
>time to process a message.
Thanks for the help! Problem was with data that I sent to the server, in test
app it was slightly different from production
--
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
