当前在线人数17174
首页 - 分类讨论区 - 电脑网络 - 窗口里的风景版 - 同主题阅读文章

此篇文章共收到打赏
0

  • 10
  • 20
  • 50
  • 100
您目前伪币余额:0
未名交友
[更多]
[更多]
.Net remoting vs web service
[版面:窗口里的风景][首篇作者:LodossWar] , 2003年10月21日22:24:31 ,282次阅读,0次回复
来APP回复,赚取更多伪币 关注本站公众号:
[分页:1 ]
LodossWar
进入未名形象秀
我的博客
[回复] [回信给作者] [本篇全文] [本讨论区] [修改] [删除] [转寄] [转贴] [收藏] [举报] [ 1 ]

发信人: LodossWar (sleepycat), 信区: DotNet
标  题: .Net remoting vs web service
发信站: Unknown Space - 未名空间 (Tue Oct 21 22:47:03 2003) WWW-POST

My words on this issue:
.Net remoting is more flexible and should be used for performance
reason.


http://www.developer.com/net/net/print.php/11087_2201701_1

ASP.NET Web Services: 1
.NET Remoting: 2
- Protocol: 
  1. Can be accessed only over HTTP
  2. Can be accessed over any protocol (including TCP, HTTP, SMTP and so on)
- State Management:
  1. Web services work in a stateless environment
  2. Provide support for both stateful and stateless environments through
Singleton and SingleCall objects
- Type System:
  1. Web services support only the datatypes defined in the XSD type system,
limiting the number of objects that can be serialized.
  2. Using binary communication, .NET Remoting can provide support for rich
type system
- Interoperability:
  1. Web services support interoperability across platforms, and are ideal for
heterogeneous environments.
  2. .NET remoting requires the client be built using .NET, enforcing
homogenous environment. 
- Reliability:
  1.  Highly reliable due to the fact that Web services are always hosted in
IIS
  2. Can also take advantage of IIS for fault isolation. If IIS is not used,
application needs to provide plumbing for ensuring the reliability of the
application. 
- Extensibility:
  1. Provides extensibility by allowing us to intercept the SOAP messages
during the serialization and deserialization stages.
  2. Very extensible by allowing us to customize the different components of
the .NET remoting framework. 
- Ease-of-Programming:
  1. Easy-to-create and deploy.
  2. Complex to program. 

Both the .NET remoting and ASP.NET Web services are powerful technologies that
provide a suitable framework for developing distributed applications. It is
important to understand how both technologies work and then choose the one
that is right for your application. For applications that require
interoperability and must function over public networks, Web services are
probably the best bet. For those that require communications with other .NET
components and where performance is a key priority, .NET Remoting is the best
choice. In short, use Web services when you need to send and receive data from
different computing platforms, use .NET Remoting when sending and receiving
data between .NET applications. In some architectural scenarios, you might
also be able to use.NET Remoting in conjunction with ASP.NET Web services and
take advantage of the best of both worlds.





--
※ 修改:·LodossWar 於 Oct 21 22:47:03 修改本文·[FROM: 151.201.]
※ 来源:.Unknown Space - 未名空间 mitbbs.com.[FROM: 151.201.]

 
[分页:1 ]
[快速返回] [ 进入窗口里的风景讨论区] [返回顶部]
回复文章
标题:
内 容:

未名交友
将您的链接放在这儿

友情链接


 

Site Map - Contact Us - Terms and Conditions - Privacy Policy

版权所有,未名空间(mitbbs.com),since 1996