域服务类是否在后台使用WCF或其他服务框架,还是从头开始呢？
解决方法
Our thinking on the RIA Services work really grow out of the LINQ project a few years ago. LINQ integrates query semantics into the languages (C#,VB,etc) providing a common abstraction for working with data; whether that data is in memory CLR objects,XML,relational data,or anything else. With RIA Services we are extending this pattern by offering a prescriptive model for exposing your domain logic over LINQ. We think of domain logic as that part of your application that is very specific to your domain – that is the particular business problem you are solving.
那么LINQ就是“域逻辑”,而WCF本质上只是一个服务提供者.
在传统的N层开发中,这意味着：
…you should think of RIA services as a more perceptive layer on top of ADO.NET Data Services and WCF… We also expect to eventually provide full access to all the power and flexibility from the underlying WCF services such as highly optimized binary serialization.
或者您还可以选择使用新的“RIA服务模式”：
…build ASP.NET applications easily while taking advantage of all the built in features of RIA Services such as data validation,authorization,etc. In the march preview,we are offering a asp:DomainDataSource control that enables very easy ASP.NET WebForms access to your domain logic. Building on top of that is a future version of ASP.NET Dynamic Data that makes it very easy to generate common,standard UI based on your domain logic.
这意味着RIA服务可以：
>坐在WCF的顶部(基本上包装客户端应用程序的WCF服务消费).
>使用交替数据源(例如,根据Building A Data-Driven Expense App with Silverlight 3的ADO.NET实体数据模型/实体框架)将RCF服务替换为WCF层
另外值得注意的是Mix09: Building Amazing Business Applications with Silverlight 3.
在我写这篇文章的时候,我刚刚发现了Microsoft’s .NET RIA Services Overview,它看起来像是解释了RIA服务背后的很多理性(可能比上面的一些更清楚:)
版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 [email protected] 举报，一经查实，本站将立刻删除。