Boost logo

Boost :

From: Jeff Garland (jeff_at_[hidden])
Date: 2002-03-20 10:27:33

> well its in the code - though its not obvious . The key is that all
> objects are written and read back in EXACTLY the same order. Hence
> we now what class to expect so we don't have to read if from the
> file. For polymorphic pointers, the procedure is the same though has
> subtlties that can only be understood by reviewing the code. The
> basic trick is that we "register" the derived class pointers in the
> same order when we load and save so we can identify the class with
> the object id which is portable. If one is truely interested you can
> follow the code while displaying the charater serialize file.

I haven't looked at your code, so this may be a bit off-track, but I'll just say
that depending on the 'order of things in the stream' (including attributes)
will not work for a database archiver. Databases queries don't preserve the
ordering in the way that streaming to a file or network does. So if you want to
have databases as an option, the archiver has to have enough data/control to
decode things.


Boost list run by bdawes at, gregod at, cpdaniel at, john at