WCF的OData多平台的发展？ [英] WCF OData for multiplatform development?

问题描述

在这个问题的OP询问使用WCF / OData的作为内部数据访问层。

The OP in this question asks about using an WCF/OData as an internal data access layer.

<一个href=\"http://stackoverflow.com/questions/2498796/arguments-of-using-wcf-odata-as-access-layer-instead-of-ef-l2s-nhibernate-direct\">Arguments使用WCF / OData的接入层，而不是EF / L2S / NHibernate的直接

一个响亮的回答似乎不这样做。我在相似的位置到OP，但在原来的问题没有提出一个问题。我想开发（原生）了很多不同的平台，但要保留尽可能多的数据和业务逻辑服务器端尽可能的。所以，我要的iOS / Android版/网络（MVC）/桌面应用程序。目前，我有一个ORM的数据访问层单一的WinForms应用程序（LLBLGEN专业版）。

The resounding reply seems to be don't do it. I'm in similar position to the OP, but have a concern not raised in the original question. I'm trying to develop (natively) for a lot of different platforms but want to keep as much of the data and business logic server side as possible. So I'll have iOS/Android/Web (MVC)/Desktop applications. Currently, I have a single WinForms applications with an ORM data access layer (LLBLGen Pro).

我预想（与LLBLGEN或其他ORM还可能）将大部分我的业务/数据访问逻辑的背后WCF / OData的接口。然后，使得在不同的平台非常薄（基本上UI和WCF调用），我所有的不同的客户端。

I'm envisioning moving most of my business / data access logic (possibly still with LLBLGen or other ORM) behind a WCF / OData interface. Then making all my different clients on the different platforms very thin (basically UI and WCF calls).

时这也是过度设计？我缺少一个简单的解决方案？

Is this also overengineered? Am I missing a simpler solution?

推荐答案

我看不到在你的架构问题或认为这是overengeenered作为OData的是一个标准的协议和你的概念符合DRY原则为好。

I cannot see any problem in your architecture or consider it overengeenered as a OData is a standard protocol and your concept conforms the DRY principle as well.

我改变了一个问题：为什么你会实现每个客户推出更多可能的错误和适度宽松的单一和集中的地方，修正错误的可能性相同的业务逻辑。你的想法使你能够实现安全层只有一次。

I change the question: Why would you implement the same business logic in each client to introduce more possible bugs and loose the possibility to fix the errors at one single and centralized place. Your idea makes you able to implement the security layer only once.

的OData是一个跨平台的标准，你可以找到每个开发平台的OData库（的 MSDN ， OData.org ，的 JayData为JavaScript ）。此外，还可以使用OData的FunctionImports /服务的方法和实体层面的方法，这将简化您的查询。

OData is a cross-platform standard and you can find a OData libraries for each development platform (MSDN, OData.org, JayData for JavaScript). Furthermore, you can use OData FunctionImports/Service methods and entity-level methods, which will simplify your queries.

这篇关于WCF的OData多平台的发展？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！