.Net Remoting: Wrap user objects vs more remoting channels -
I am learning about remoting small remote-based projects and to avoid my behavior, I am trying to implement the habit of developing bad habits.
is a service that uses plugins created by user. Each plugin is separated into its own appdomain. Additionally, there is a client application that connects and interacts with the service.
Service-customer communications and service-plugins are channels for communication, but there is nothing to facilitate plug-in client communications such as service-defining an object created by a plug-in The object must be wrapped before it can reach the customer (otherwise there is an exception due to lack of channel sync).
If it makes sense, my question is, should I continue this method or should I create a channel between the plugin and the client epideman so that plug-in instant objects to go to the client application Allow?
Thanks for any education topic!
I can not give a definitive answer without hearing more about your application, so the question is a rational subjective Here's my subjective answer:
It seems that the server connects to plugins, and the client only holds the same channel on the server. It simplifies and consolidates the solution in many ways:
- Access control done only in server
- Plugin mechanism can be made transparent to the client. >
- Simplified Clients around
- In the case of placing clients and servers on separate machines, you would prefer the client to talk only on the server and not directly from any plug-ins, Because it may require many connections / Ndergahon for Khulana (each plug on the server machine-In), if you have firewalls, etc., it could become a problem.
On the other hand, this envelope may be a problem plug-object in a server object
Comments
Post a Comment