DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=35760>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35760 ------- Additional Comments From [EMAIL PROTECTED] 2005-08-11 21:28 ------- My concern with CoInitializeEx(NULL,COINIT_MULTITHREADED) is that it breaks any object which wants to CoInitialize(NULL), which might include any given ODBC or other win32-specific extentions. That said, I've never seen an issue in most cases. I agree with your suggested patch, and we'll just have to call out STRONGLY in the CHANGES file that this behavior may cause them problems. However, if a module early-on initializes the thread CoInitialize(NULL), we should still fall back on this model, wouldn't you agree? E.g. HRESULT hr = CoInitializeEx(NULL, COINIT_MULTITHREADED); if (hr == RPC_E_CHANGED_MODE) hr = CoInitialize(NULL); Do you suppose we should emit a debug notice in the fallback-mode? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
