On Fri, 5 Oct 2007 08:29:50 -0700 "Robert Ramey" wrote:
There are two issues with the serialization library
a) Its not currently thread safe b) Serialization code can be duplicated in different shared libraries. It's not clear what this implies.
The first is on a path to final solution. It will depend upon the existence a thread-safe lazily initialized singleton which will have to be provided by the user until boost has such a thing (if that ever happens).
Hi Robert, I'd like to use Boost serialization in threaded applications and am thrilled to hear that you have a solution in mind. Are there any (possibly simple?) rules that you could state that would guarantee thread-safe use with existing Boost serialization versions? I've run some simple examples using Boost serialization with threads and it seems to work correctly if all the objects to be serialized and the serialization streams are owned (write-able) by exactly one thread. Are there any guarantees that a one-thread-owns-it-all or perhaps some other approaches are safe with the current implementation? Many thanks! Ed -- Edward H. Hill III, PhD | ed@eh3.com | http://eh3.com/