24 Aug
2007
24 Aug
'07
10:26 p.m.
Robert Ramey wrote:
Michael Marcin wrote:
As I recall, the problem with the thread-safety of the serialization library relates to setting up the type info maps. If you could somehow create a way that one could invoke the setup of this map perhaps by a function call, that would solve the problem, yes?
Actually that's what happens now under the covers. This occurs in a number of different places - each in its own way. This can be factored out into a common singleton implementation. Replacing this common one with a threadsafe version will make the serialization truely threadsafe.
That sounds good. Will you let us know when you have something to look at? Thanks, Sohail