在Web上支持Windows应用程序服务的解决方案是什么？ [英] what is the solution to support windows application services on the web?

问题描述

在我们公司，我们有一个企业Windows应用程序，现在我们决定在Web上发布一些业务服务，让Web客户端使用我们的企业应用程序。我们怎么做到的？考虑因素： - Web客户端具有低速Internet。 - Web应用程序将支持一些业务用例。 - 我们需要高安全性来使用这些服务。 - 我们使用C＃.net，Sql server和asp.net



我们正在考虑两个解决方案：







解决方案1：

第一个型号的图片





解决方案2

第二个模特的图片







哪种型号更好？你有另一种解决方案吗？



感谢您的关注...

解决方案

您只有一个问题：您可能认为架构是绘制框，云和连接线，带有一些标题。它不是。建筑是所有思想的拳头。这是你几乎错过的东西。



让我们从第二张图片开始，因为这是明显的胡言乱语。你在右侧加上标题LAN，里面的一个元素称为Web App。我错过了什么吗？您是否打算让我们相信万维网可以了解局域网中放置的某些Web应用程序？我不这么认为。请注意，在那个可怕的客户端 - 服务器模型中，活动部分只是客户端，服务器正在侦听和被动，仅根据客户端的请求执行操作。连接到Internet的LAN上的客户端可以向暴露于Internet的Web应用程序发送请求，但Internet上的任何内容都不能在LAN中请求任何内容，除非它连接到同一LAN。



第一张照片不太明显，但也有：什么是Windows App？你明白应该是一个服务应用程序吗？ （我不知道你的意思，也许只是Windows OS上的一些应用程序，但Windows应用程序通常用于提及一些带UI的应用程序。）Windows在这里几乎无关紧要。可以从Web和LAN使用的服务应该完全从操作系统中抽象出来。从技术上讲，这很有可能，即使只使用C＃也是如此。另外，您是否认为未连接到LAN的CLR客户端。您可以拥有更薄的Web客户端（基于浏览器）和更厚的CLR客户端，具有额外的功能和/或性能？您应该意识到的一件事是：由于HTTP协议的无状态特性和客户端 - 服务器模型的支配，Web对功能施加了严格的限制。在绘制与内容相关的内容之前，您应该了解在这些限制下工作的想法。到目前为止，如果没有关于什么是应用程序和客户端的一些信息，查看这些图片甚至绘制类似的东西都没有多大意义。但基本上，第一张图片意味着开始思考正确的方向。



请理解：不是说你的模特是好还是不好，不管是不是。他们根本不是模特。考虑到这些图片还不够严肃。提出什么建议？好吧，在尝试绘制架构之前，做一些技术研究和一些基本的原型设计，尽可能简单（但不简单:-)）。



< DD> -SA

In our company we have an enterprise windows application, Now we have decided to publish some of the business services on the web and let web clients to work with our enterprise application. How we can do it ? with considerations: - The web clients have low speed Internet. - The Web application is going to support some of the business use cases. - We need high security for using the services. - We use C#.net , and Sql server and asp.net

We are thinking of two solutions :



Solution 1:
picture for first model


Solution 2
picture for second model



which model is better ? do you have another solution?

Thanks for your attention...

解决方案

You have only one problem: you probably think that architecture is drawing boxes, clouds and connecting lines, with some captions. It is not. Architecture is fist of all some thinking. And this is something which you pretty much missed.

Let's start from the second picture, because this is the apparent gibberish. You put a caption "LAN" on right side, and one element inside is called "Web App". Am I missing something? Are you going to convince us that "World Wide Web" can be aware of some "Web App" placed in "LAN"? I don't think so. Note that in that dreaded client-server model, the active part is only the client, and the server is listening, and passive, acting only on request of the clients. A client on the LAN connected to Internet can send requests to the Web application exposed to internet, but nothing on the Internet cannot request anything in the LAN, unless it is connected to the same LAN.

The first picture is less obvious, but also: what is "Windows App"? Do you understand that is should be a service application? (I don't know what you meant to say, maybe just "some application on Windows OS", but "Windows Application" is usually used to mention some application with UI.) "Windows" is pretty much irrelevant here. The service, to be usable from both the Web and LAN, should be totally abstracted from the OS. Technically, this is quite possible, even with C# only. Also, did you think about CLR clients not connected to your LAN. You could have thinner Web clients (browser based) and thicker CLR clients, with extra capabilities and or performance? One thing you should realize is: Web imposes draconian limitations on the functionality, due to stateless nature of HTTP protocol and domination of client-server model. Before drawing what is connected to what, you should learn the ideas of working under these limitations. So far, without some information on what is the "application" and "clients", looking at this picture and even drawing something similar does not make much sense. But very basically, first picture means starting to think in right direction.

Please understand: not that your "models" are good or not, correct or not. They are not models at all. Considering those pictures is just not serious enough. What to advise? Well, before trying to "draw" the architecture, do some technological research and some basic prototyping, as simple as possible (but not simpler :-)).

—SA

这篇关于在Web上支持Windows应用程序服务的解决方案是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！