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? *** Just refrain from creating more than one archive at a time. Actually, since the need from multiple open archives is not a common scenarrio, This has been a problem only very few people have actually had. Of course this is small consolation for those that actually have it. Are there any guarantees that a one-thread-owns-it-all or perhaps some other approaches are safe with the current implementation? *** one thread owns all serialization would work as would using your semaphore to guarentee the above Robert Ramey