ADO.NET 数据服务在整体设计中的地位 [英] ADO.NET data services their place in overall design

问题描述

ADO.NET 数据服务是应用程序中的下一代数据访问层.我已经看到很多示例直接从 Silverlight 或 Ajax 等 UI 层使用它来获取数据.这几乎就像有一个两层系统，完全删除了业务层.DAL 应该由业务层访问，而不是直接从 UI 访问吗?

ADO.NET Data service is the next generation of data access layer within applications. I have seen a lot of examples using it directly from a UI layer such as Silverlight or Ajax to get data. This is almost as having a two tiered system, with business layer completely removed. Should DAL be accessed by the Business layer, and not directly from UI?

推荐答案

ADO.NET 数据服务是另一种需要评估以移动数据的工具.

ADO.NET Data Services is one more tool to be evaluated in order to move data.

.NET RIA 服务是另一个.我会说好多了.

.NET RIA Services is another one. Much better I would say.

我将 ADO.NET 数据服务视为供某些人使用的低级服务高级框架.我不会让我的 UI 直接与它对话.

I see ADO.NET Data Services as a low level services to be used by some high level framework. I would not let my UI talk directly to it.

我看到的 ADO.NET 数据服务的主要问题更多地与安全性高于其他任何东西.

The main problem I see with ADO.NET Data Services has more to do with security than with anything else.

对于简单/快速的任务，在 Intranet 中，如果您不太挑剔设计，它可以是有用的.(海事组织)当您需要从现有数据库快速公开数据时，它会非常方便.

For simple/quick tasks, in a Intranet, and if you are not too pick with your design, it can be useful. (IMO) It can be quite handy when you need to quickly expose data from an existing database.

我说方便，但这不会是我的第一选择，因为我会尽量避免快速而肮脏"的解决方案.那些解决方案就像鬼魂，总是回来缠着你.

I say handy, but it would not be my first choice as I avoid as much as I can the "quick and dirty" solutions. Those solutions are like ghosts, always come back to haunt you.

这篇关于ADO.NET 数据服务在整体设计中的地位的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！