🚀 go-pugleaf

"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