In message <[EMAIL PROTECTED]> on Sat, 27 Apr 2002 19:08:42 +0200,
Bogusław Brandys <[EMAIL PROTECTED]> said:
brandysb> Yep.But what about COMP_zlib() function ? I would like to add zlib
brandysb> internally into SSL transmission (I know that this way would be not
brandysb> standard but don't care since it will be internal client/server
brandysb> software).And what about compression level in that case , can i set this
brandysb> freely ?
In the ssltest.c program that comes with 0.9.7, there's some example
code. In short, you'd do the following:
/* This constant is completely non-standard, it just happens to be the
number used in ssltest.c. Unfortunately, there is no standard
number yet, although there's rumours about a draft assigning a
number somewhere
Note that this constant will ONLY work with other programs using
the exact same constans for zlib compression. In effect, this
becomes rather useless unless you design all the programs that are
going to communicate with each other... */
#define COMP_ZLIB 2
/* ... */
COMP_METHOD = COMP_zlib();
/* ... */
/* Do this really early, before creating any SSL/TLS streams */
SSL_COMP_add_compression_method(COMP_ZLIB, cm);
/* ... */
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
