Hi Brian. Yeah, c++ serialization is a pain. One reason I'm a huge fan of c#.
Why not use ssl for an encrypted compressed connection to your server? Openssl is easy to use and a standard protocol that would save time from re-inventing the wheel. Chris On Sat, Jan 9, 2010 at 3:47 PM, Brian <[email protected]> wrote: > > I'm considering using crypto++ in an on line alternative to > serialization > libraries that I'm working on -- http://webEbenezer.net. > > Currently this program -- > http://webEbenezer.net/build_integration.html > uses bzip2 to compress data sent between users and > our site. I hope to also add encryption to the processing. > I don't know much about encryption, though and am > wondering how to figure out (narrow down) what > classes to use from crypto++. > > > I've read that generally compression is done first and > then encryption. Does that match your experience? > > > I ran cryptest e inputfile outputfile > > The input file was 133 bytes and the output file was > 176 bytes. Does encryption usually iincrease the > number of bytes like that? I haven't tried it yet with > a larger file to see if the increase is proportional to > the size of the file or not. > > Thanks in advance. > > -- > You received this message because you are subscribed to the "Crypto++ Users" > Google Group. > To unsubscribe, send an email to [email protected]. > More information about Crypto++ and this group is available at > http://www.cryptopp.com. >
-- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com.
