Re: .Net Service provider XmlSerialization problems

[email protected] Fri, 21 May 2004 07:57:39 +0200
Newsgroups gmane.comp.sourceid.sso.devel
Message-ID <OF588C4CAE.2763B8B9-ON42256E9B.002043AC-42256E9B.0020BE58@sanlam.co.za>
hi David

Yes, the Microsoft serializer is not thread safe, which I realised when=
 I
ran my first test yesterday after making the serializer static ;-). How=
 I
got around this is I just put a lock on the object when I used the
serialize method. This seemed to work great, we did a load test with 25=
0
users simultaneously, and each login was done in less than 3 seconds, a=
nd
the assemblies in the cache stayed stable all the way.

I just want to say thanx to Tum from dotgnu for explaining the working =
of
the serializer to me. Quite ironic that my answer came from the open so=
urce
world ;-).

Thanx for your reply as well David.
ciao
Willem Smit
SL IT
9471637
0724872442

***************
Any views expressed in this message are those of the individual sender,=
 and
Sanlam accepts no liability therefore, except where the sender specific=
ally
states them to be those of Sanlam.
Enige sienswyses of stellings wat in hierdie boodskap uitgedruk word is=
 di=E9
van die individuele afsender, en Sanlam aanvaar geen aanspreeklikheid
daarvoor nie, behalwe waar die afsender uitdruklik vermeld dat dit di=E9=
 van
Sanlam is.
=