.Net远程处理-设计/体系结构 [英] .Net Remoting - Design/Architecture

问题描述

所有大师，

我将使用.Net Remoting开发一种与服务器进行通讯的应用程序，并想知道设计它的最佳方法是什么.

我有4个屏幕，这些屏幕或多或少地与4个表相对应，并且我还有几个其他表可以将其他表链接"在一起.

问题是:
如果我只有一个/一对服务器激活对象来提供获取/设置功能并处理庞大的数据集，以作为一种来回发送数据的方式，会更好吗?

或

拥有一堆更好地(几乎一对一)代表域对象的服务器激活对象并在服务器端处理数据库是否会很好?例如人员，帐户，交易，TransactionFinder，PersonFinder等...

任何帮助，不胜感激.如果您能指出解决该问题的文章，那就太好了.

谢谢，
Prashant

All Gurus,

I am about to develop an application with .Net Remoting as a way to talk to the server and was wondering what would be the best way to design it.

I have 4 screens that correspond more or less to 4 tables, and I have a couple of more tables that "link" other tables together.

Question is:
Would it be better if I had only a one/couple Server Activated Objects that provide a Get/Set functions and deal with huge DataSets as a way of sending data back-n-forth?

OR

Would it be good to have a bunch of Server Activated objects that represent the Domain Objects better(almost one-to-one) and deal with the database on the server side? e.g. Person, Account, Transaction, TransactionFinder, PersonFinder etc....

Any help greatly appreciated. It will be great if you could point me to articles that address this issue.

Thanks,
Prashant

推荐答案

一些远程处理指南此处.

在实现远程处理之前，您可能还希望先了解一下WCF.

Some remoting guidelines here.

You might also want to look at WCF before you implement remoting.

远程处理是很麻烦的.我没有WCF比较的性能指标，但是滚动自己的代码始终是更好的性能选择，而不是为了方便起见而不使用Microsoft提供的功能.当然，滚动自己的代码会花费更长的时间...

Remoting is a slug. I have no performance metrics for a WCF comparison, but rolling your own code is always a better performance choice rather than using what Microsoft provides for the sake of convenience. Of course, rolling your own code takes a bit longer...

这篇关于.Net远程处理-设计/体系结构的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！