首页 \ 问答 \ AppDomains之间的通信(Communication between AppDomains)

AppDomains之间的通信(Communication between AppDomains)

 我们正在构建一个应用程序（WinForms，.NET 3.5），它将“插件”DLL加载到辅助AppDomain中。 辅助AppDomain需要偶尔与第一个AppDomain通信（更具体地说，从主AppDomain中创建的对象调用或获取数据）。  
 我已经阅读了有关AppDomains的大部分内容以及它们之间的通信。  
 到目前为止，我见过的唯一简单的解决方案是从MarshalByRefObject继承并将TransparentProxy传递到第二个AppDomain，在Proxy上调用方法。  
 此方法有其缺点（例如，在框架类型的情况下，或者从已经从其他类继承的类型，静态字段/类等等，并不总是可以从MBRO继承）。  
 由于当前的通信点非常不变（只有2-3个需要通信的场景），我考虑创建一个具有以下属性的简单Mediator类：  
 
  将在1st（Main）AppDomain中创建。  
  只能作为主要AppDomain中创建的“Real”对象的“消息传递器”。  
  将继承自MBRO，并将其代理引用发送到第二个AppDomain。  
 
 将调用此代理对象上的方法，然后调用第一个AppDomain中“真实”对象上的方法。  
 我的问题 -  
 
  这看起来像是一个逻辑设计吗？  
  更重要的是，WCF或任何其他通信框架中是否已存在调解器/消息传递器类？ 它似乎是一个通用的概念，我想知道是否有类似的东西。  

We are building an app (WinForms, .NET 3.5) that loads "Plugin" DLLs into a secondary AppDomain. The secondary AppDomain needs to communicate occasionally with the 1st one (more specifically, call or get data from objects that are created in the main AppDomain). 
I have read most of the material about AppDomains and communication between them. 
So far, the only easy solution i've seen was inheriting from MarshalByRefObject and passing a TransparentProxy into the 2nd AppDomain, calling methods on the Proxy. 
This method has its drawbacks (not always possible to inherit from MBRO in case of framework types for example, or types that already inherit from another class, static fields/classes and so on). 
Since the current communication points are pretty constant (only 2-3 scenarios that require communication), i have considered creating a simple Mediator class with the following properties: 
 
 Will be created in the 1st (Main) AppDomain. 
 Would function only as a "message-passer" to the "Real" objects that are created in the main AppDomain. 
 Will inherit from MBRO, and a proxy reference to it will be sent to the 2nd AppDomain. 
 
Methods on this proxy object would be called, which in turn will call the methods on the "real" objects in the 1st AppDomain. 
My questions -- 
 
 Does this seem like a logical design? 
 More importantly, does a mediator/message passer class already exist in WCF or any other communcation framework? it seems like a generic concept and i am wondering if there is something similar. 

原文：https://stackoverflow.com/questions/8972352

更新时间：2023-11-07 17:11

最满意答案

 您必须在实际调用之前设置方法期望，因此您的测试应如下所示：  
context "Get #show" do
  subject { get :show, school_id: school.id, id: user.id }

  it "calls +authorize+ befor action" do
    expect(controller).to receive(:authorize)
    subject
  end
end
 
 查看文档https://github.com/rspec/rspec-mocks#message-expectations 

You must set method expectation before actual call, so your test should look like: 
context "Get #show" do
  subject { get :show, school_id: school.id, id: user.id }

  it "calls +authorize+ befor action" do
    expect(controller).to receive(:authorize)
    subject
  end
end
 
Check the documentation https://github.com/rspec/rspec-mocks#message-expectations

AppDomains之间的通信(Communication between AppDomains)

最满意答案

相关问答

下列中不属于面向对象的编程语言的是?[2022-05-30]

Rails测试控制器方法，在过滤器之前设置实例变量(Rails Testing controller methods with instance variables set in before filters)[2021-10-23]

Rails类别（或过滤器）链接在同一控制器中？(Rails category (or filter) links in same controller?)[2023-09-05]

在rails中，控制器的before过滤器中调用的方法是否针对每个操作运行？(In rails, does a method called in the before filter of a controller run for every action?)[2022-03-01]

如何在rspec控制器测试期间记录rails控制器过滤器(How to log rails controller filters during rspec controller tests)[2022-11-23]

使用来自控制器的操作作为轨道中另一个控制器的过滤器(Use action from a controller as filter in another controller in rails)[2022-07-01]

在rails控制器中测试之前的过滤器(Testing a before filter in rails controller)[2023-11-03]

在RAILS API控制器索引操作中应用过滤器哈希是否有DRY方法？(Is there a DRY approach to applying a filter hash in a RAILS API controller index action?)[2023-09-20]

通过rails控制器过滤数据(Filter data through rails controller)[2024-01-10]

Rails - 在另一个控制器中使用过滤器参数(Rails - Using filter parameters in another controller)[2023-01-06]

相关文章

最新问答