后端的一般架构？
我们正在努力在我们正在设计的一些新系统的架构选择上具有前瞻性。我们几乎想要构建后端系统，无论我们决定使用什么界面（WinForms、Silverlight、MVC、Webforms、WPF、IOS（iPad/Iphone）等...），我相信这就是 REST。我们的组织通常只会使用 Microsoft API，但由于我不知道 WCF-Web-Api 何时发布，而且我们希望尽快开始，所以看起来我们别无选择。
我们希望在此采取一些小步骤来增加购买的机会。所以我们不想再设置一台带有 IIS 的服务器。
在可预见的将来，我们将只使用 WinForms 和 WinForms。网络表单。我的想法是我们可以在本地计算机上使用 Nancy，但以 RESTFul 的方式与其进行通信。这样，将来它应该像设置服务器并将所有客户端重定向到该服务器而不是本地一样简单。
我从未使用过 NancyFX 或 OpenRasta，但是，据我所知，它听起来很合适。
所以问题是：
- 我正在思考的解决这个问题的方式是一个好方法
- 吗？听起来 NancyFX 或 OpenRasta 会更合适吗？
- 我们为什么应该等待 WCF-Web-API，如果是的话，有人有大概的发布日期吗？
We are trying to be forward looking in our architecture choice on some of the new systems we are designing. Pretty much we want to architecture back end system that no matter what interface we decide to use (WinForms, Silverlight, MVC, Webforms, WPF, IOS (IPad/Iphone), ect...) which i believe just screams REST. Our organization generally will only use Microsoft APIs but since i have no idea when WCF-Web-Api will be released and we want to get started soon it looks like we have no other choice.
We want to take baby steps here to increase the chances of buy off. So we don't want to have to set up another server with IIS.
In the foreseeable future we will only be using WinForms & WebForms. What i was thinking we could use Nancy on the local machine but communicate with it in a RESTFul way. That way in the future it should be as simple as setting up a server and redirecting all the clients to that server rather than locally.
I've never used either NancyFX or OpenRasta, but, from what ive heard, it sounded like a good fit.
So the questions are:
- Is the way i'm thinking on approaching this a good approach
- Does it sound like NancyFX or OpenRasta would be a better fit?
- Any reason why we should wait for WCF-Web-API and if so does anyone have an approx release date.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
OpenRasta 是为面向资源的场景而构建的。您可以使用任何其他框架实现相同的目标（或多或少有痛苦）。 OpenRasta 为您提供了一个完全组合的、IoC 友好的环境，可以完全解耦处理程序和呈现它们的任何内容（这使得它不同于 nancy 和 MVC 等 MVC 框架）。
我想补充一点，我们有一个非常强大的社区，一个稳定的代码库，我们已经在这方面工作了好几年了，我们正在构建 2.1 和 3.0，我们的功能集仍然超出了您可以从大多数其他产品获得的功能系统。将此与您强调的大多数框架进行比较，其中没有一个达到 1.0。
如果这是您公司的决定因素，我们还可以提供专业支持。
但要完全回答你的问题，根据你的场景和你想要实现的目标，只要有足够的工作，你就可以做出任何适合的事情。我建议根据架构而不是框架重新表述您的问题。
OpenRasta was built for resource-oriented scenarios. You can achieve the same thing with any other frameworks (with more or less pain). OpenRasta gives you a fully-composited, IoC friendly environment that completely decouples handlers and whatever renders them (which makes it different from MVC frameworks like nancy and MVC).
I'd add that we have a very strong community, a stable codebase and we've been in this for quite a few years, we're building 2.1 and 3.0 and our featureset is still above and beyond what you can get from most other systems. Compare this to most of the frameworks you've highlighted, where none have reached 1.0.
Professional support is also available, if that's a deciding factor for your company.
But to answer your question fully, depending on your scenario and what you want to achieve, you can make anything fits, given enough work. I'd suggest reformulating your question in terms of architecture rather than in terms of frameworks.