[serialization] Binary archive headers?

Hi, I'm looking at the streambuf filled with data after I do this: boost::asio::streambuf buf; std::ostream stream( &buf ); boost::archive::binary_oarchive archive( stream ); archive << "Hello World"; And I see that there's a lot of binary data that preceeds the "Hello World" data. Looks like custom header information that boost::serialization inserts into the stream. Is there a way to prevent any automatic header information from being inserted into the archive's stream? I'm using this serialized buffer to communicate with a device over a COM port and I can't have this extra information in my buffer. Thanks. --------- Robert Dailey

At 6:03 PM -0500 8/25/09, Robert Dailey wrote:
Hi,
I'm looking at the streambuf filled with data after I do this:
boost::asio::streambuf buf; std::ostream stream( &buf ); boost::archive::binary_oarchive archive( stream ); archive << "Hello World";
And I see that there's a lot of binary data that preceeds the "Hello World" data. Looks like custom header information that boost::serialization inserts into the stream. Is there a way to prevent any automatic header information from being inserted into the archive's stream? I'm using this serialized buffer to communicate with a device over a COM port and I can't have this extra information in my buffer.
Include the boost::archive::no_header flag in the optional second argument to the archive constructor.

look for "no_header" argument on archive constructor.
Robert Ramey
"Robert Dailey"
participants (3)
-
Kim Barrett
-
Robert Dailey
-
Robert Ramey