🚀 go-pugleaf

Well it did not help:

delay comes from :

procedure TIdSSLIOHandlerSocketOpenSSL.ConnectClient;
on StartSSL; call

inside StartSSL it calls Init which calls

procedure TIdSSLIOHandlerSocketOpenSSL.Init;
begin
   if not Assigned(fSSLContext) then begin
     fSSLContext := TIdSSLContext.Create;
.
.
.




constructor TIdSSLContext.Create;
begin
   inherited Create;

   if DLLLoadCount <= 0 then begin
   	if not IdSSLOpenSSL.LoadOpenSLLibrary then begin
     	raise 	 
EIdOSSLCouldNotLoadSSLLibrary.Create(RSOSSLCouldNotLoadSSLLibrary);
     end;
   end;
   Inc(DLLLoadCount);

   fVerifyMode := [];
   fMode := sslmUnassigned;
   fSessionId := 1;
end;

So this line:

IdSSLOpenSSL.LoadOpenSLLibrary takes lots of time to execute. and I do 
that after IdSSLOpenSSLHeaders::Load();

So I am still not sure how to avoid it :(


Oleg Tiktinski wrote:
> Sorry too fast to post I found Load - let me check if it will help.
> 
> 
> Oleg Tiktinski wrote:
>> I am using BCB2007 ( or CodeGear 2007 C++ Builder), Indy10 and I can't 
>> find  IdSSLOpenSSLHeaders.Load();
>>
>> there is file IdSSLOpenSSLHeaders.hpp, but I don't see Load anywhere 
>> there. :(
>>
>>
>>
>> Remy Lebeau (TeamB) wrote:
>>> "Oleg Tiktinski" <oleg@sequoiars.com> wrote in message 
>>> news:483cc31b$1@newsgroups.borland.com...
>>>
>>>> I am using Indy tcp client with SSL
>>>
>>> Which version of Indy are you using?
>>>
>>>> I did some research and find out that on first use
>>>> Indy call LoadSSLLibrary function
>>>
>>> There is no LoadSSLLibrary() function in Indy.  There is a Load() 
>>> function in the IdSSLOpenSSLHeaders unit, though.
>>>
>>>> which do tons of work and slow things down.
>>>
>>> Indy dynamically loads each WinSock DLL function on an as-needed 
>>> basis.  I do not know why Indy never did the same thing with the SSL 
>>> functions.  Most likely to make sure that they are all available 
>>> before allowing any SSL code to run.
>>>
>>>> Did anyone else had this issue ? Any workaround ?
>>>
>>> There is no workaround without re-writing how Indy loads the SSL 
>>> functions internally.
>>>
>>>> Problem is that I can't call this function directly
>>>
>>> Yes, you can.  The IdSSLOpenSSLHeaders.Load() function is publically 
>>> accessible.
>>>
>>>> I have to make FAKE SSL connection in order for Indy to call 
>>>> LoadSSLLibrary.
>>>
>>> No, you don't.
>>>
>>>
>>> Gambit
>>>