I always put the libraries in the application folder.
For one application, I probably need to switch to another library.
I tested RTC yesterday (RealThinClient).
It can use commercial SSL libraries like SecureBlackBox of which I have a
license of an older version.
But after a simple test , I'll discard RTC
ICS with SSL was twice as fast as RTC with plain http.
It's not so thin either, the compiled exe was 126 kb larger and there's
another 200kb for SecureBlackBox , but the complete package would be smaller
because I don't need openSsl .
Using cab compression, the 2 openSSl libraries are still 613 kB
Paul
----- Original Message -----
From: "Arno Garrels" <arno.garr...@gmx.de>
To: "ICS support mailing" <twsocket@elists.org>
Sent: Sunday, July 26, 2009 10:02 AM
Subject: Re: [twsocket] ICS V7 bug ?
Angus Robertson - Magenta Systems Ltd wrote:
Here is an article from Microsoft concerning the msvcr71.dll and
where to place it. Another case of DLL hell.
The only safe way to install an ICS SSL application is to install the
two or three SSL and runtime DLLs in the same directory as the
program. Otherwise you may get conflicts with other applications also
using OpenSSL but using different SSL version DLLs that are either
installed in the windows directory or available via a path (as is
Subversion). I learnt this the hard way, installing Subversion
broke one of my servers. Several FTP clients also use OpenSSL.
I recently managed to build OpenSSL with C++ Builder, so one was
able link .obj files rather than the libraries, though I'm not sure
whether OpenSSL license allowed this for closed-source applications.
--
Arno Garrels
--
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
--
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
