To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=93051
------- Additional comments from [EMAIL PROTECTED] Wed Aug 27 10:09:41 +0000 2008 ------- When I left configmgr it was very much threading-capable. The UnoApiLock was obviously introduced by mmeeks in the configrefactor01 CWS. FWIW: I would not have accepted any attempt do introduce such a global lock for everything, completely eliminating thread awareness in configmgr, had I still been the maintainer. While the original implementation may have had overengineered concurrency support, a lock that is even shared between independent ConfigurationProvider instances runs completely counter to the design of the component. Taking a lock just for queryInterface is obviously broken, but I suppose getting rid of that won't help much if the calling thread also wants to invoke actual API functionality. Having the separate cache write-back thread perform its (complex) work under a global lock that excludes any API activity is also utterly broken, but it may take more analysis to determine whether it is safe to get rid of that lock (I also haven't found the place where that thread takes the global lock). --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
