标签云

微信群

扫码加入我们

WeChat QR Code

I have an application that needs to send a moderately high volume of messages between a number of AppDomains.I know that I could implement this using remoting, but I have also noticed that there are cross-domain delegates.Has anyone looked at this kind of problem?


WCF using named pipes looks like the favourite to me - I can then at least avoid the necessity of going onto the network.Thanks everyone!

2019年09月18日00分19秒

Care to elaborate about this technique? for example, what's the performance cost of using named pipes and the ease of use compared with AppDomains and MBRO (MarshalByRefObject).

2019年09月18日00分19秒

I don't have any figures to hand, but using a binary serializer and named pipes has allowed me to communicate pretty much seamlessly between domains.I came up with a simple message bus and have been able to simply ignore the problem ever since.

2019年09月18日00分19秒

Remoting sound .NET 1.1 to me. Is there any newer alternatives for doing cross-appdomain communication?

2019年09月18日00分19秒

Remoting never went away. It's still used everywhere. The modernation of WCF came for cross process (IPC) calls. But for appdomains, it's always been remoting. You could use WCF with named pipes, but meh. Remoting is less hassle IMO.

2019年09月18日00分19秒

x0n, [Remoting is] a legacy technology that is retained for backward compatibility with existing applications and is not recommended for new development. Distributed applications should now be developed using theWindows Communication Foundation (WCF). msdn.microsoft.com/library/72x4h507.aspx

2019年09月18日00分19秒

Guillaume Yep, I agree - I probably should have made the distinction clearer, but it was four years ago :D

2019年09月18日00分19秒

This works between ANY two domains, not just parent child.+1

2019年09月19日00分19秒