Serialization API improvements #27
Description
Currently the field serialization API supports only files/filenames for reading and writing.
Some applications might need to integrate the field serialization into their own data serialization (e.g. append to some custom file stream) and therefore store (or read) the serialized field into a larger file together with other information.
A possible starting point could be a new Load()/Store() variant that takes an external memory buffer and writes (or reads) into it.
Another useful feature for the serialization API would be versioning support.
As a start, it would be nice to have at least a way of rejecting the load of fields that are created with OpenPGL incompatible with the one the application is currently using.
Ideally the serialization API could support backwards compatibility and try to load fields from older OpenPGL versions without rejecting them.