From: Dean M. B. <mik...@gm...> - 2010-02-19 15:41:16
|
On Thu, Feb 18, 2010 at 11:27 PM, Nelson, Erik - 2 <eri...@ba...> wrote: > From: Dean Michael Berris on Thursday, February 18, 2010 12:56 AM > >>Unfortunately because we support HTTPS, we require OpenSSL everytime. >>There should be a way to disable it though. > > A few things to think about in the discussion > > --there are a number of SSL providers available... OpenSSL, MatrixSSL, > MS Windows API If Boost.Asio works with any of these, then you should be able to link to them. > --OpenSSL may be packaged with most GNU/Linux distributions, but it's > not on Windows Yes. Although the choice of OpenSSL is made by Boost.Asio. Where Boost.Asio works, cpp-netlib should work too. > --OpenSSL has a dependency on Perl to build on MS Windows, so an > additional dependency is created (Perl is not packaged with Windows) > > I understand that the effect could be made with a define like > BOOST_NETLIB_NO_SSL, but that seems like a big hammer... Is there no > other way to pay for only what you use (http, in this case)? > There should be a compile-time option for that, although it's not yet implemented. Boost.Asio has a way of turning off SSL support too. > As an aside, I previously investigated building both MatrixSSL and > OpenSSL into my portable (Windows/Linux) app and found MatrixSSL much > simpler to work with. > Again, if Boost.Asio works with it then it should be doable. cpp-netlib depends on Boost.Asio to provide the SSL support and functionality at the transport level. cpp-netlib is much higher level for that. -- Dean Michael Berris cplusplus-soup.com | twitter.com/deanberris linkedin.com/in/mikhailberis | facebook.com/dean.berris | deanberris.com |