From: JOLY Loic (loic.joly_at_[hidden])
Date: 2003-11-07 11:49:23
I plan to use serialisation, but not to save data in a file, but to send
it over the network. I wonder wether the serialisation library draft
would be relevent to my case.
Among the requirements described in the overview, there are some for
which I do not care, and other not written that I am not sure are
totally adressed by the library.
I do not care (and do not want to pay) for 3 and 5 (versionning and
handling of shared data).
What I need is self-contained data. For instance, when I send an object
on the network, I do not want any globally shared table of object
references, or class definition, to be generated.
I believe that the object_serializable implementation level could help
me in that respect, but would like to specify it not at the class level,
but at the archive level. That way, I am sure all classes sent to my
archive behave correctly. Is this possible ?
Do you think I could use serialisation to achieve my goals ? Do you
think there is another point I forgot ?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk