There shouldn't be any issues here or at least we haven't had any reported and it's not obvious what it could be. One thing to consider if you're coming from a CPython background is that IronPython doesn't have a global interpreter lock and therefore there won't be any implicit locking done for you. In the case of static methods that shouldn't matter much because .NET design guidelines state that all static methods should be thread safe.
The only other thing I could think of is that it's somehow related to value types or reference types given that you said it's related to argument-types - maybe re-using and mutating the same boxed value type? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sakesun Roykiattisak Sent: Friday, May 09, 2008 3:13 AM To: users@lists.ironpython.com Subject: [IronPython] Any known clr-interop concurrency issue ? Hi, I'm currently trouble-shooting concurrency issue in my IP server-application. I suspect that IP(1.1.1) has issue that concurrent calls to static method with certain argument-type can cause corruption. I'm going to try making a demonstration project tonight. However, to save my time, I wonder if there are any already known concurrency issue in IP 1.1.1 ? Or if anybody have some hint for me to find the exact problem ? Thanks. _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
