"Jorge Lodos" <lodos@segurmatica.cu> wrote in message news:007801c66577$3a129dd0$f9010a0a@segurmatica.cu...
I mean that only one property (which of course could contain others) could be loaded (or saved) at a time. Not the whole tree. For instance, if my tree corresponds to a windows registry key, it is desirable to load or save a single value without loading or saving all the values in the key.
I am quite sure Serialization lib will allow you to do this. Just apply it to appropriate field.
It requires a lot of work.
How come?
The serialization library does not provide a model for in-memory property storage,
It's not supposed to. std::vector, std::map, multi_index, tree - take your pick
nor does it provide a windows registry archive (the last time I saw).
Ok - Implement one. No need to reinvent the whole infrastructure.
Applying serialization to appropriate fields implies I already have those fields somehow organized.
Why? Or rather what do you mean by that.
The way I see it, PT is the serialization library plus in-memory property storage.
The way I see it we already have better solution for either task.
Perhaps it could have used serialization internally and serialization archives for loading and saving.
Better stop reinventing the wheel and just write an add-ons to excising solution.
As I said before, the real difference could be the loading and saving of some of the properties in the memory storage, without having to load/save them all.
I still do not see any difficulties implementing this without PT. Gennadiy