Hello, we are currently working on using Boost Serialization to read and write generic graph structures to/from file.
Below we have a simple & generic directed graph container. Our goal is to serialize this structure to file. We do not know ahead of serialization / de-serialization what the full shape of the graph is. In both directions we only have the graph container.
We create an empty graph and add nodes / edges randomly to create our test structure. This is a graph where multiple nodes can point to the same node, including themselves.
Here is an example use case. We create a random graph and serialize it to file. Then, somewhere else, we open the file and read the graph back in. How do we tell the serialization function how to allocate nodes that have not been visited yet, and to reuse nodes if they have already been visited.
Any support would be great. We have poured over the documentation and communities such as stack overflow but have not been able to find advice on such variable and shared allocations.
Thanks,
Joss Whittle
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, we are currently working on using Boost Serialization to read and write generic graph structures to/from file.
Below we have a simple & generic directed graph container. Our goal is to serialize this structure to file. We do not know ahead of serialization / de-serialization what the full shape of the graph is. In both directions we only have the graph container.
We create an empty graph and add nodes / edges randomly to create our test structure. This is a graph where multiple nodes can point to the same node, including themselves.
Here is an example use case. We create a random graph and serialize it to file. Then, somewhere else, we open the file and read the graph back in. How do we tell the serialization function how to allocate nodes that have not been visited yet, and to reuse nodes if they have already been visited.
Any support would be great. We have poured over the documentation and communities such as stack overflow but have not been able to find advice on such variable and shared allocations.
Thanks,
Joss Whittle