[英]Which do I choose for hosting my in-proc server in a separate process - COM+ or DCOM?
I need to shield a 64-bit COM component consumer from the 32-bit native C++ ATL in-proc COM component. 我需要从32位本机C ++ ATL进程内COM组件中屏蔽64位COM组件使用者。
Seems like both COM+ and DCOM can host my in-proc component in a separate process and do the marshalling so that both me and the consumer application don't care of it and I even don't have to change my in-proc component at all. 好像COM +和DCOM都可以在一个单独的进程中托管我的In-proc组件并进行编组,这样我和使用者应用程序都不必理会它,甚至不必在该位置更改我的In-proc组件。所有。 I tried both - both seem to "just work" after some initial use of the hammer for setting up the COM+ application or the DCOM application respectively. 我尝试了两种方法-分别在最初使用锤子分别设置COM +应用程序或DCOM应用程序后,两者似乎都“正常工作”。
I need a solution that would be the best in terms of deployment and problems diagnosing at the customers'. 我需要一个在部署和客户问题诊断方面最好的解决方案。 Which do I choose - COM+ or DCOM? 我该选择哪个-COM +或DCOM?
They're both working, so the choice doesn't seem that important. 他们都工作,所以选择不似乎是重要的呢。 I would choose COM+ because: 我之所以选择COM +,是因为:
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.